The Linux Manuals (man pages) document is an important part of Linux documents. Linux Manuals are organized as several sections. Each section has a group of commands for a specific area in Linux usage, administration or development.
bundle-show – Shows all the gems in your bundle, or the path to a gem Synopsisbundle show [GEM] [–paths] DescriptionWithout the [GEM] option, show will print a list of the names and versions of all gems that are required by your [Gemfile(5)][Gemfile(5)], sorted by name. Calling show with [GEM] will list the exact location of…
bundle-remove – Removes gems from the Gemfile Synopsisbundle remove [GEM [GEM …]] [–install] DescriptionRemoves the given gems from the Gemfile while ensuring that the resulting Gemfile is still valid. If a gem cannot be removed, a warning is printed. If a gem is already absent from the Gemfile, and error is raised. Options–install Runs bundle…
bundle-pristine – Restores installed gems to their pristine condition Synopsisbundle pristine Descriptionpristine restores the installed gems in the bundle to their pristine condition using the local gem cache from RubyGems. For git gems, a forced checkout will be performed. For further explanation, bundle pristine ignores unpacked files on disk. In other words, this command utilizes…
bundle-platform – Displays platform compatibility information Synopsisbundle platform [–ruby] Descriptionplatform will display information from your Gemfile, Gemfile.lock, and Ruby VM about your platform. For instance, using this Gemfile(5): source "https://rubygems.org" ruby "1.9.3" gem "rack" If you run bundle platform on Ruby 1.9.3, it will display the following output: Your platform is: x86_64-linux Your app has…
bundle-package – Package your needed .gem files into your application Synopsisbundle package DescriptionCopy all of the .gem files needed to run the application into the vendor/cache directory. In the future, when running [bundle install(1)][bundle-install], use the gems in the cache in preference to the ones on rubygems.org. Git And Path GemsSince Bundler 1.2, the bundle…
bundle-outdated – List installed gems with newer versions available Synopsisbundle outdated [GEM] [–local] [–pre] [–source] [–strict] [–parseable | –porcelain] [–group=GROUP] [–groups] [–update-strict] [–patch|–minor|–major] [–filter-major] [–filter-minor] [–filter-patch] [–only-explicit] DescriptionOutdated lists the names and versions of gems that have a newer version available in the given source. Calling outdated with [GEM [GEM]] will only check for newer…
bundle-open – Opens the source directory for a gem in your bundle Synopsisbundle open [GEM] DescriptionOpens the source directory of the provided GEM in your editor. For this to work the EDITOR or BUNDLER_EDITOR environment variable has to be set. Example: bundle open ‘rack’ Will open the source directory for the ‘rack’ gem in your…
bundle-lock – Creates / Updates a lockfile without installing Synopsisbundle lock [–update] [–local] [–print] [–lockfile=PATH] [–full-index] [–add-platform] [–remove-platform] [–patch] [–minor] [–major] [–strict] [–conservative] DescriptionLock the gems specified in Gemfile. Options–update=<*gems> Ignores the existing lockfile. Resolve then updates lockfile. Taking a list of gems or updating all gems if no list is given. –local Do not…
bundle-list – List all the gems in the bundle Synopsisbundle list [–name-only] [–paths] [–without-group=GROUP] [–only-group=GROUP] DescriptionPrints a list of all the gems in the bundle including their version. Example: bundle list –name-only bundle list –paths bundle list –without-group test bundle list –only-group dev bundle list –only-group dev –paths Options–name-only Print only the name of each…
bundle-install – Install the dependencies specified in your Gemfile Synopsisbundle install [–binstubs[=DIRECTORY]] [–clean] [–deployment] [–frozen] [–full-index] [–gemfile=GEMFILE] [–jobs=NUMBER] [–local] [–no-cache] [–no-prune] [–path PATH] [–quiet] [–redownload] [–retry=NUMBER] [–shebang] [–standalone[=GROUP[ GROUP…]]] [–system] [–trust-policy=POLICY] [–with=GROUP[ GROUP…]] [–without=GROUP[ GROUP…]] DescriptionInstall the gems specified in your Gemfile(5). If this is the first time you run bundle install (and a Gemfile.lock…
bundle-inject – Add named gem(s) with version requirements to Gemfile Synopsisbundle inject [GEM] [VERSION] DescriptionAdds the named gem(s) with their version requirements to the resolved [Gemfile(5)][Gemfile(5)]. This command will add the gem to both your [Gemfile(5)][Gemfile(5)] and Gemfile.lock if it isn’t listed yet. Example: bundle install bundle inject ‘rack’ ‘> 0’ This will inject the…
bundle-init – Generates a Gemfile into the current working directory Synopsisbundle init [–gemspec=FILE] DescriptionInit generates a default [Gemfile(5)][Gemfile(5)] in the current working directory. When adding a [Gemfile(5)][Gemfile(5)] to a gem with a gemspec, the –gemspec option will automatically add each dependency listed in the gemspec file to the newly created [Gemfile(5)][Gemfile(5)]. Options–gemspec Use the specified…
bundle-info – Show information for the given gem in your bundle Synopsisbundle info [GEM] [–path] DescriptionPrint the basic information about the provided GEM such as homepage, version, path and summary. Options–path Print the path of the given gem
bundle-gem – Generate a project skeleton for creating a rubygem Synopsisbundle gem GEM_NAME OPTIONS DescriptionGenerates a directory named GEM_NAME with a Rakefile, GEM_NAME.gemspec, and other supporting files and directories that can be used to develop a rubygem with that name. Run rake -T in the resulting project for a list of Rake tasks that can…
bundle-exec – Execute a command in the context of the bundle Synopsisbundle exec [–keep-file-descriptors] command DescriptionThis command executes the command, making all gems specified in the [Gemfile(5)][Gemfile(5)] available to require in Ruby programs. Essentially, if you would normally have run something like rspec spec/my_spec.rb, and you want to use the gems specified in the [Gemfile(5)][Gemfile(5)]…
bundle-doctor – Checks the bundle for common problems Synopsisbundle doctor [–quiet] [–gemfile=GEMFILE] DescriptionChecks your Gemfile and gem environment for common problems. If issues are detected, Bundler prints them and exits status 1. Otherwise, Bundler prints a success message and exits status 0. Examples of common problems caught by bundle-doctor include: • Invalid Bundler settings •…
bundle-config – Set bundler configuration options Synopsisbundle config [list|get|set|unset] [name [value]] DescriptionThis command allows you to interact with Bundler’s configuration system. Bundler loads configuration settings in this order: 1. Local config (app/.bundle/config) 2. Environmental variables (ENV) 3. Global config (~/.bundle/config) 4. Bundler default config Executing bundle config list with will print a list of all…
bundle-clean – Cleans up unused gems in your bundler directory Synopsisbundle clean [–dry-run] [–force] DescriptionThis command will remove all unused gems in your bundler directory. This is useful when you have made many changes to your gem dependencies. Options–dry-run Print the changes, but do not clean the unused gems. –force Force a clean even if…
bundle-check – Verifies if dependencies are satisfied by installed gems Synopsisbundle check [–dry-run] [–gemfile=FILE] [–path=PATH] Descriptioncheck searches the local machine for each of the gems requested in the Gemfile. If all gems are found, Bundler prints a success message and exits with a status of 0. If not, the first missing gem is listed and…
bundle-cache – Package your needed .gem files into your application Synopsisbundle cache DescriptionCopy all of the .gem files needed to run the application into the vendor/cache directory. In the future, when running [bundle install(1)][bundle-install], use the gems in the cache in preference to the ones on rubygems.org. Git And Path GemsThe bundle cache command can…