bundle - Ruby Dependency Management
bundleCOMMAND [--no-color] [--verbose] [ARGS]
Bundler manages an
application's dependencies through its entire life
across many machines systematically and repeatably.
Print all output without color
Print out additional logging information
bundle subcommands into primary commands and utilities.
Install the gems specified by the
Update dependencies to their latest versions
Package the .gem files required by your application into the
Execute a script in the context of the current bundle
Specify and read configuration options for bundler
Display detailed help for each subcommand
Add the named gem to the Gemfile and run
Generate binstubs for executables in a gem
Determine whether the requirements for your application are installed and available to bundler
Show the source location of a particular gem in the bundle
Show all of the outdated gems in the current bundle
Start an IRB session in the context of the current bundle
Open an installed gem in the editor
Generate a lockfile for your dependencies
Generate a visual representation of your dependencies
Generate a simple
Gemfile, placed in the current directory
Create a simple gem, suitable for development with bundler
Display platform compatibility information
Clean up unused gems in your bundler directory
Display warnings about common potential problems
When running a command that isn't listed in PRIMARY COMMANDS or UTILITIES,
Bundler will try to find an executable on your path named
and execute it, passing down any extra arguments to it.
Bundler includes a feature called trampolining, designed to allow a single developer to work on multiple projects, each on different Bundler versions. The trampoline will infer the correct version of Bundler to use for each project and load that version instead of the version directly invoked (which is almost always the newest version installed locally).
Bundler by default will use the Bundler version in the current directory to
determine the version to trampoline to, reading from the
BUNDLED WITH section.
However, if the
BUNDLER_VERSION environment variable is set, that version will
override the lockfile inference and can be used in directories without a
Until the target version is Bundler 2 or later,
be set for the trampoline to be used. Additionally,
be set to completely disable the trampoline.
These commands are obsolete and should no longer be used