wordmove-ng 6.0.0

data/CONTRIBUTING.md

@@ -0,0 +1,114 @@
+Welcome to the contributor guide. If you can't find important information you're welcome
+to edit this page or [open a discussion](https://github.com/tekgnosis-net/wordmove-ng/discussions/new?category=general) to talk with maintainers.
+
+In this guide you'll find informations about:
+* [Bug reporting](#bug-reporting)
+* [Development](#development)
+* [Maintainer tasks](#maintainer-tasks)
+
+### Bug reporting
+
+wordmove-ng is an hard piece of software to debug and it is used by many users with many
+different environments - Windows also, even if it isn't officially supported by the dev team.
+
+So *please*, follow the issue template when reporting a bug.
+
+If you're not sure if you're standing in front of a bug, please [open a discussion](https://github.com/tekgnosis-net/wordmove-ng/discussions/new?category=general)
+labeling it as "Triage", possibly using this template to report your problem (note: GH's discussions does not support templates ATM):
+
+```markdown
+**Describe the bug**
+
+> A clear and concise description of what the bug is.
+
+**Wordmove command**
+
+> Command used on the CLI: (e.g.: `wordmove-ng pull --all --no-db`)
+
+**Expected behavior**
+
+> A clear and concise description of what you expected to happen.
+
+**movefile.yml**
+
+> Paste (removing personal data) the interesting part, if any, of your `movefile.yml` formatting it inside a code block with `yml` syntax and double checking the indentation.
+
+**Exception/trace**
+
+> Paste (removing personal data) the entire trace of error/exception you encountered, if any
+
+**Environment (please complete the following information):**
+
+- OS:
+- Ruby: (`ruby --version`)
+- wordmove-ng: (`wordmove-ng --version`)
+
+**Doctor**
+
+* [x] running the `wordmove-ng doctor` command returns all green
+
+> (If it is not, report the error you got.)
+```
+
+As a general advise: only the latest stable wordmove-ng release is supported. Bugs in the legacy `wordmove` 5.x gem belong to its own tracker.
+We'd appreciate your help opening an in depth report if you'd find that an older version is working
+better for you.
+
+Thank you all for your support and for the love <3
+
+### Development
+
+#### Get Wordmove
+
+* fork wordmove-ng
+* clone your own repo
+* be sure to check-out the right branch, usually `master`
+
+##### Installing Ruby
+
+To install ruby, please, use [rbenv](https://github.com/rbenv/rbenv) or [RVM](https://rvm.io).
+
+##### Contribute
+
+* run `bundle install` to install gem dependencies
+* `git checkout -b my_feature_or_fix_name`
+* code, commit, push and send a pull request on GitHub
+
+> Never bump the version or edit CHANGELOG.md by hand: both are generated by
+> release-please from the commit messages. Write [Conventional Commits](https://www.conventionalcommits.org):
+> `fix: ...` (patch), `feat: ...` (minor), `feat!: ...` or a `BREAKING CHANGE:` footer (major),
+> plus `docs:`, `chore:`, `ci:`, `test:`, `refactor:` for everything that does not ship a change.
+
+
+##### Test Wordmove
+
+Wordmove has a decent test coverage. We _require_ that pull requests does not break tests launched by the CI.
+In order to launch tests on you dev machine
+
+```fish
+bundle exec rake
+```
+
+The command will launch the test suite - written with RSpec - and rubocop. Ruby 3.0 or
+newer is required; the CI matrix covers 3.0 through 4.0.
+
+In order to use the gem locally you can install it
+
+```fish
+bundle exec rake install
+wordmove-ng --version
+```
+
+or run the executable directly
+
+```fish
+bin/wordmove-ng --version
+```
+
+### Maintainer tasks
+
+ToDo:
+
+* [ ] versioning and version dumping
+* [ ] changelog/release
+* [ ] publishing the gem

data/Gemfile

@@ -0,0 +1,14 @@
+source 'https://rubygems.org'
+
+# Runtime dependencies live in wordmove-ng.gemspec
+gemspec
+
+group :development, :test do
+  gem "bundler", ">= 2.0", "< 5"
+  gem "priscilla", "~> 1.0"
+  gem "pry-byebug", "~> 3.1"
+  gem "rake", "~> 13.0"
+  gem "rspec", "~> 3.13"
+  gem "rubocop", "~> 1.90"
+  gem "simplecov", ">= 0.22", "< 2"
+end

data/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2013-2019 weLaika Soc. Coop. (Wordmove)
+Copyright (c) 2026 Kumar, tekgnosis.net (wordmove-ng changes)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.md

@@ -0,0 +1,340 @@
+# wordmove-ng
+
+![logo](assets/images/wordmove-ng.png)
+
+wordmove-ng moves WordPress sites between environments. One command pushes or pulls
+the core, uploads, themes, plugins, mu-plugins, languages and the database between a
+local install and any number of remote hosts over SSH, rewriting URLs and paths on the
+target with wp-cli.
+
+It is the maintained, independent successor of [Wordmove](https://github.com/welaika/wordmove)
+by weLaika, continued through the [kokiddp fork](https://github.com/kokiddp/wordmove).
+The movefile format, commands and flags are unchanged. What changed is under the hood, and
+in a few places where the old behaviour was unsafe. See [Upgrading from wordmove 5.x](#upgrading-from-wordmove-5x).
+
+[![Tests](https://github.com/tekgnosis-net/wordmove-ng/actions/workflows/ruby.yml/badge.svg)](https://github.com/tekgnosis-net/wordmove-ng/actions/workflows/ruby.yml)
+
+## Highlights
+
+- **No Ruby-side SSH.** Every remote operation goes through the system `ssh`, `scp` and
+  `rsync`, so your agent, `~/.ssh/config`, jump hosts and modern key types all just work,
+  and nothing breaks on a new OpenSSL or Ruby.
+- **The source database is never written.** Push and pull both dump the source, import on
+  the target and run `wp search-replace` on the target.
+- **Fails before it breaks anything.** Prerequisites on both sides are probed before any
+  backup, dump or import. `wordmove-ng doctor` checks SSH authentication and remote programs
+  per environment.
+- **Optional maintenance mode** around the target's database replacement.
+- MariaDB first (`mariadb`, `mariadb-dump`) with MySQL fallback, sandbox-header handling,
+  collation and charset normalisation, socket and port support.
+- Runs on Ruby 3.0 through 4.0.
+
+## Installation
+
+Ruby 3.0 or newer is required.
+
+```bash
+gem install wordmove-ng
+```
+
+Until the gem is on rubygems.org, or to run the latest master:
+
+```bash
+gem install specific_install
+gem specific_install https://github.com/tekgnosis-net/wordmove-ng.git
+```
+
+From a checkout:
+
+```bash
+bundle install
+bin/wordmove-ng --help
+```
+
+## Quick start
+
+```bash
+cd /path/to/your/wordpress   # where wp-config.php lives
+wordmove-ng init             # writes movefile.yml, pre-filled from wp-config.php
+wordmove-ng doctor           # validates movefile.yml, local tools, SSH auth, remote tools
+wordmove-ng pull -e staging --all
+wordmove-ng push -e production -t -p   # themes and plugins only
+wordmove-ng push -e production -d -s   # simulate a database push
+```
+
+Run `wordmove-ng help` for all commands and `wordmove-ng help push` for the flags.
+Component flags: `-w` core, `-u` uploads, `-t` themes, `-p` plugins, `-m` mu-plugins,
+`-l` languages, `-d` database, `--all` everything (`--all --no-uploads` to exclude one).
+`-s` simulates, `-e` picks the environment, `-c` points at another movefile.
+
+## Peer dependencies
+
+wordmove-ng is orchestration glue around standard tools.
+
+**Locally**
+
+| Program | Needed for |
+| --- | --- |
+| `ssh`, `scp`, `rsync` | every remote operation |
+| `sshpass` | only when `ssh.password` is set in the movefile |
+| `gzip` | database sync |
+| `mysqldump` or `mariadb-dump` | `push -d` (dumping the local database) |
+| `mysql` or `mariadb` | `pull -d` (importing into the local database) and `doctor` |
+| `wp` ([WP-CLI](https://wp-cli.org)) | `pull -d` (adapting the local database) |
+
+**On each remote**, in the `$PATH` of a non interactive login
+
+| Program | Needed for |
+| --- | --- |
+| `rsync`, `gzip` | file and database sync |
+| `mysqldump` or `mariadb-dump` | `pull -d` |
+| `mysql` or `mariadb`, `wp` | `push -d` |
+
+`wordmove-ng doctor` reports exactly what is missing where, and every database operation
+re-checks before doing anything.
+
+## SSH authentication
+
+Everything uses the system `ssh` client. When no `ssh.password` is configured, connections run
+with `BatchMode=yes`: a failing key authentication is reported as an error with the exact
+command that failed, never an interactive password prompt.
+
+- `ssh.host`, `ssh.user`, `ssh.port` map to the obvious ssh options. A host configured in
+  `~/.ssh/config` works with only `ssh.host` set.
+- `ssh.password` is passed through `sshpass` to `ssh`, `scp` and `rsync`. Keys are strongly
+  preferred.
+- `ssh.gateway` becomes `ssh -J`. The jump host must accept your key or agent; a
+  `gateway.password` cannot be honoured and is ignored (doctor warns).
+- `ssh.rsync_options` are appended to the rsync command.
+
+Remote commands always run through `sh -c`, so the remote login shell may be bash, zsh,
+fish or csh.
+
+## Database sync
+
+Both directions have the same shape: dump the source, import the dump on the target, run
+`wp search-replace` on the target for `vhost` and `wordpress_path`. The source database is
+only ever read.
+
+- `wordmove-ng pull -d`: back up the local database, dump the remote, import locally,
+  search-replace locally.
+- `wordmove-ng push -d`: back up the remote database, dump locally, import on the remote,
+  search-replace on the remote over SSH.
+
+Backups are written to the local `wp-content/` directory as timestamped `.sql.gz` files
+before any import. If the remote adaptation fails after the import, the log names the
+backup to restore from.
+
+`wp search-replace` runs with `--all-tables --skip-columns=guid`, so every table in the
+target database is adapted, including non WordPress tables sharing it, and post GUIDs are
+left alone as WordPress recommends. `--no-adapt` skips the search-replace entirely.
+
+If one of the four search terms is a prefix of another (for example a local vhost of
+`https://site.test` and a remote of `https://site.test.example.com`) the shorter replacement
+also rewrites the longer value. Doctor reports this as an error and the DB step warns.
+
+### Maintenance mode
+
+```yaml
+global:
+  maintenance_mode: true
+```
+
+wraps the target's import and search-replace in `wp maintenance-mode activate` and
+`deactivate`, so visitors see the WordPress maintenance page rather than a site pointing at
+the other environment's URLs for a few seconds. Deactivation runs even when the adaptation
+fails. `WORDMOVE_MAINTENANCE_MODE=1` forces it on for a single run. Default: off.
+
+### MariaDB and MySQL compatibility
+
+- `mariadb` and `mariadb-dump` are preferred when present, falling back to `mysql` and
+  `mysqldump`.
+- Dumps starting with the MariaDB sandbox header (`/*!999999- enable the sandbox mode */`)
+  import cleanly on older servers.
+- Imports run with `--binary-mode`, `SET FOREIGN_KEY_CHECKS=0` and a trailing `COMMIT;`,
+  unless `mysql_options` already sets binary mode.
+- `database.socket` and `database.port` are first-class; `--socket` inside
+  `mysql_options` or `mysqldump_options` still works.
+- Newer `utf8mb3` collations are rewritten to `utf8mb4_unicode_ci` and `utf8mb3` to
+  `utf8mb4` before import. Override or extend the mappings:
+
+```yaml
+global:
+  collation_fallbacks:
+    utf8mb3_uca1400_ai_ci: utf8mb4_unicode_ci
+  charset_fallbacks:
+    utf8mb3: utf8mb4
+```
+
+- `wp` is always called with `--allow-root`, so root-owned Docker installs work.
+
+## `movefile.yml`
+
+```yaml
+global:
+  maintenance_mode: false
+
+local:
+  vhost: http://vhost.local
+  wordpress_path: /home/john/sites/your_site
+
+  database:
+    name: database_name
+    user: user
+    password: password
+    host: localhost
+    # port: 3306
+    # socket: /path/to/mysql.sock
+
+production:
+  vhost: https://example.com
+  wordpress_path: /var/www/your_site
+
+  database:
+    name: database_name
+    user: user
+    password: password
+    host: host
+    # mysqldump_options: --max_allowed_packet=50MB
+    # mysql_options: --protocol=TCP
+
+  exclude:
+    - ".git/"
+    - ".env"
+    - "node_modules/"
+    - "wp-config.php"
+    - "wp-content/*.sql.gz"
+
+  ssh:
+    host: host
+    user: user
+    # port: 22
+    # password: only with sshpass installed; prefer keys
+    # rsync_options: --verbose
+    # gateway:
+    #   host: bastion.example.com
+    #   user: jump
+
+  # forbid:
+  #   push:
+  #     db: true          # never push the database to production
+  # hooks:
+  #   push:
+  #     before:
+  #       - command: echo "about to push"
+  #         where: local
+  #     after:
+  #       - command: wp cache flush
+  #         where: remote
+  #         raise: false
+```
+
+Every first-level key other than `global` and `local` is a remote environment; pick one with
+`-e`. `movefile.yml` is evaluated as ERB, so secrets can come from the environment or from
+a `.env` / `.env.<environment>` file next to it:
+
+```yaml
+production:
+  database:
+    password: "<%= ENV['PROD_DB_PASS'] %>"
+```
+
+File sync mirrors the source: files missing on the source are deleted on the destination.
+Put anything you need to keep in `exclude`, which is always relative to `wordpress_path`.
+
+The wiki has the full reference:
+[movefile.yml configurations explained](https://github.com/tekgnosis-net/wordmove-ng/wiki/movefile.yml-configurations-explained),
+[Usage and flags explained](https://github.com/tekgnosis-net/wordmove-ng/wiki/Usage-and-flags-explained),
+[Multiple environments explained](https://github.com/tekgnosis-net/wordmove-ng/wiki/Multiple-environments-explained),
+[Hooks](https://github.com/tekgnosis-net/wordmove-ng/wiki/Hooks).
+Where a wiki page still describes wordmove 5.x behaviour, this README wins.
+
+## Logging
+
+Long generated shell scripts are summarised into intent lines such as
+`dump database my_db to ./wp-content/dump.sql`, `compress ./wp-content/dump.sql`,
+`wp search-replace old.test -> new.test in /var/www/site` and
+`import SQL dump ... (strip sandbox header, append COMMIT)`. Passwords, hosts, vhosts and
+paths from the movefile are masked as `[secret]` in all output, including hook output.
+
+## Upgrading from wordmove 5.x
+
+This applies to both the original `wordmove` gem and the kokiddp fork. Your `movefile.yml`
+keeps working with the exceptions below.
+
+1. **Install the new gem and use the new command.** `gem install wordmove-ng`, then call
+   `wordmove-ng` instead of `wordmove`. Both gems can stay installed side by side.
+2. **Ruby 3.0 or newer.** Ruby 2.6 and 2.7 are no longer supported.
+3. **Put `wp` on your remotes.** `push -d` now adapts the database on the remote, so WP-CLI
+   must be installed there and be in the `$PATH` of a non interactive login. It is a single
+   PHAR file: [installing WP-CLI](https://wp-cli.org/#installing). Run `wordmove-ng doctor`
+   to confirm.
+4. **FTP and SFTP are gone.** A movefile with an `ftp` block fails with a clear error. FTP
+   only ever existed for shell-less shared hosts, where the database had to be handled by
+   uploading temporary PHP scripts and URLs were rewritten in the dump with a regex. Keep the
+   legacy `wordmove` 5.x gem for such hosts, or move them to SSH.
+5. **`global.sql_adapter` is ignored.** URL and path adaptation always uses wp-cli on the
+   target. The key is still accepted, with a warning, so old movefiles validate; remove it
+   when convenient. `database.charset` (removed in 3.0) is no longer accepted by the schema.
+6. **Push no longer touches your local database.** Old versions ran `wp search-replace`
+   on the live local database during a push and restored it afterwards, which left the local
+   site pointing at production if anything failed in between. That is gone.
+7. **SSH behaves like rsync did.** If rsync worked but the database step asked for a
+   password, the cause was the old Net::SSH library, which could not sign RSA keys with
+   SHA-2. That path no longer exists. If key authentication fails now, you get an error with
+   the failing `ssh` command instead of a prompt. `ssh.gateway.password` is ignored.
+8. **Remote programs are checked up front.** Missing `gzip`, `mysql`, `mysqldump` or `wp`
+   on either side aborts before any backup or dump, listing what is missing.
+9. **New, optional:** `global.maintenance_mode` (see above).
+
+## Contributing
+
+```bash
+bundle install
+bundle exec rake          # specs + rubocop, what CI runs
+bundle exec rspec spec/deployer/ssh_db_spec.rb   # one file
+```
+
+CI runs on Ruby 3.0, 3.1, 3.2, 3.3, 3.4 and 4.0. Please keep this README updated when
+changing user-facing behaviour, and write [Conventional Commits](https://www.conventionalcommits.org)
+(`feat:`, `fix:`, `feat!:` for breaking changes): the changelog and version number are
+generated from them. See [CONTRIBUTING.md](CONTRIBUTING.md).
+
+### Releasing
+
+Releases are automated by [release-please](https://github.com/googleapis/release-please)
+and published to [rubygems.org](https://rubygems.org/gems/wordmove-ng) with
+[trusted publishing](https://guides.rubygems.org/trusted-publishing/), so no API key is
+stored anywhere.
+
+1. Every push to `master` updates a "release PR" that bumps `lib/wordmove/version.rb` and
+   `CHANGELOG.md` according to the commits since the last release.
+2. Merging that PR creates the `vX.Y.Z` tag and the GitHub release.
+3. The `publish` job in `.github/workflows/release.yml` then runs the test suite on the
+   tagged commit, builds the gem, pushes it to rubygems.org and attaches the `.gem` file to
+   the GitHub release.
+
+Pushing a `v*` tag by hand at the head of `master` triggers the same publish job; that is
+how 6.0.0 is cut.
+
+One-time setup for a new maintainer or a fork:
+
+- On rubygems.org, under your profile's *Trusted publishers*, add a **pending** publisher
+  for gem `wordmove-ng`, repository owner `tekgnosis-net`, repository `wordmove-ng`,
+  workflow `release.yml`, environment `release`. It becomes a regular publisher, and you
+  the gem owner, after the first push.
+- In the GitHub repository settings create an environment named `release`, and under
+  *Actions → General* enable "Allow GitHub Actions to create and approve pull requests"
+  so release-please can open its PR.
+
+## Credits and licence
+
+- Wordmove was created and maintained for a decade by [weLaika](https://dev.welaika.com):
+  Stefano Verna, Ju Liu, Fabrizio Monti, Alessandro Fazzi, Filippo Gangi Dino and
+  [many contributors](https://github.com/welaika/wordmove/graphs/contributors). The
+  workflow, movefile format and most of the code are theirs.
+- [kokiddp](https://github.com/kokiddp/wordmove) kept it running on modern Ruby, OpenSSL 3
+  and MariaDB and added socket, collation and Docker support.
+- wordmove-ng is maintained by [tekgnosis.net](https://github.com/tekgnosis-net).
+
+MIT licence, see [LICENSE](LICENSE).

data/Rakefile

@@ -0,0 +1,7 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+require 'rubocop/rake_task'
+
+RSpec::Core::RakeTask.new(:spec)
+RuboCop::RakeTask.new(:rubocop)
+task default: %i[spec rubocop]

data/bin/bundle

@@ -0,0 +1,105 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+#
+# This file was generated by Bundler.
+#
+# The application 'bundle' is installed as part of a gem, and
+# this file is here to facilitate running it.
+#
+
+require "rubygems"
+
+m = Module.new do
+    module_function
+
+  def invoked_as_script?
+    File.expand_path($0) == File.expand_path(__FILE__)
+  end
+
+  def env_var_version
+    ENV["BUNDLER_VERSION"]
+  end
+
+  def cli_arg_version
+    return unless invoked_as_script? # don't want to hijack other binstubs
+    return unless "update".start_with?(ARGV.first || " ") # must be running `bundle update`
+    bundler_version = nil
+    update_index = nil
+    ARGV.each_with_index do |a, i|
+      if update_index && update_index.succ == i && a =~ Gem::Version::ANCHORED_VERSION_PATTERN
+        bundler_version = a
+      end
+      next unless a =~ /\A--bundler(?:[= ](#{Gem::Version::VERSION_PATTERN}))?\z/
+      bundler_version = $1 || ">= 0.a"
+      update_index = i
+    end
+    bundler_version
+  end
+
+  def gemfile
+    gemfile = ENV["BUNDLE_GEMFILE"]
+    return gemfile if gemfile && !gemfile.empty?
+
+    File.expand_path("../../Gemfile", __FILE__)
+  end
+
+  def lockfile
+    lockfile =
+      case File.basename(gemfile)
+      when "gems.rb" then gemfile.sub(/\.rb$/, gemfile)
+      else "#{gemfile}.lock"
+      end
+    File.expand_path(lockfile)
+  end
+
+  def lockfile_version
+    return unless File.file?(lockfile)
+    lockfile_contents = File.read(lockfile)
+    return unless lockfile_contents =~ /\n\nBUNDLED WITH\n\s{2,}(#{Gem::Version::VERSION_PATTERN})\n/
+    Regexp.last_match(1)
+  end
+
+  def bundler_version
+    @bundler_version ||= begin
+      env_var_version || cli_arg_version ||
+        lockfile_version || "#{Gem::Requirement.default}.a"
+    end
+  end
+
+  def load_bundler!
+    ENV["BUNDLE_GEMFILE"] ||= gemfile
+
+    # must dup string for RG < 1.8 compatibility
+    activate_bundler(bundler_version.dup)
+  end
+
+  def activate_bundler(bundler_version)
+    if Gem::Version.correct?(bundler_version) && Gem::Version.new(bundler_version).release < Gem::Version.new("2.0")
+      bundler_version = "< 2"
+    end
+    gem_error = activation_error_handling do
+      gem "bundler", bundler_version
+    end
+    return if gem_error.nil?
+    require_error = activation_error_handling do
+      require "bundler/version"
+    end
+    return if require_error.nil? && Gem::Requirement.new(bundler_version).satisfied_by?(Gem::Version.new(Bundler::VERSION))
+    warn "Activating bundler (#{bundler_version}) failed:\n#{gem_error.message}\n\nTo install the version of bundler this project requires, run `gem install bundler -v '#{bundler_version}'`"
+    exit 42
+  end
+
+  def activation_error_handling
+    yield
+    nil
+  rescue StandardError, LoadError => e
+    e
+  end
+end
+
+m.load_bundler!
+
+if m.invoked_as_script?
+  load Gem.bin_path("bundler", "bundle")
+end

data/bin/bundler

@@ -0,0 +1,17 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+#
+# This file was generated by Bundler.
+#
+# The application 'bundler' is installed as part of a gem, and
+# this file is here to facilitate running it.
+#
+
+require "pathname"
+ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../../Gemfile",
+  Pathname.new(__FILE__).realpath)
+
+require "rubygems"
+require "bundler/setup"
+
+load Gem.bin_path("bundler", "bundler")

data/bin/byebug

@@ -0,0 +1,29 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+#
+# This file was generated by Bundler.
+#
+# The application 'byebug' is installed as part of a gem, and
+# this file is here to facilitate running it.
+#
+
+require "pathname"
+ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../../Gemfile",
+  Pathname.new(__FILE__).realpath)
+
+bundle_binstub = File.expand_path("../bundle", __FILE__)
+
+if File.file?(bundle_binstub)
+  if File.read(bundle_binstub, 150) =~ /This file was generated by Bundler/
+    load(bundle_binstub)
+  else
+    abort("Your `bin/bundle` was not generated by Bundler, so this binstub cannot run.
+Replace `bin/bundle` by running `bundle binstubs bundler --force`, then run this command again.")
+  end
+end
+
+require "rubygems"
+require "bundler/setup"
+
+load Gem.bin_path("byebug", "byebug")

data/bin/coderay

@@ -0,0 +1,29 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+#
+# This file was generated by Bundler.
+#
+# The application 'coderay' is installed as part of a gem, and
+# this file is here to facilitate running it.
+#
+
+require "pathname"
+ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../../Gemfile",
+  Pathname.new(__FILE__).realpath)
+
+bundle_binstub = File.expand_path("../bundle", __FILE__)
+
+if File.file?(bundle_binstub)
+  if File.read(bundle_binstub, 150) =~ /This file was generated by Bundler/
+    load(bundle_binstub)
+  else
+    abort("Your `bin/bundle` was not generated by Bundler, so this binstub cannot run.
+Replace `bin/bundle` by running `bundle binstubs bundler --force`, then run this command again.")
+  end
+end
+
+require "rubygems"
+require "bundler/setup"
+
+load Gem.bin_path("coderay", "coderay")