bundle
COMMAND [--no-color] [--verbose] [ARGS]
Bundler manages an application's dependencies
through its entire life
across many machines systematically and repeatably.
See the bundler website for information on getting
started, and Gemfile(5) for more information on the Gemfile
format.
-
--no-color
: Print all output without color -
--retry
,-r
: Specify the number of times you wish to attempt network commands -
--verbose
,-V
: Print out additional logging information
We divide bundle
subcommands into primary commands and utilities:
-
bundle install(1)
: Install the gems specified by theGemfile
orGemfile.lock
-
bundle update(1)
: Update dependencies to their latest versions -
bundle package(1)
: Package the .gem files required by your application into thevendor/cache
directory -
bundle exec(1)
: Execute a script in the current bundle -
bundle config(1)
: Specify and read configuration options for Bundler -
bundle help(1)
: Display detailed help for each subcommand
-
bundle add(1)
: Add the named gem to the Gemfile and runbundle install
-
bundle binstubs(1)
: Generate binstubs for executables in a gem -
bundle check(1)
: Determine whether the requirements for your application are installed and available to Bundler -
bundle show(1)
: Show the source location of a particular gem in the bundle -
bundle outdated(1)
: Show all of the outdated gems in the current bundle -
bundle console(1)
: Start an IRB session in the current bundle -
bundle open(1)
: Open an installed gem in the editor -
bundle lock(1)
: Generate a lockfile for your dependencies -
bundle viz(1)
: Generate a visual representation of your dependencies -
bundle init(1)
: Generate a simpleGemfile
, placed in the current directory -
bundle gem(1)
: Create a simple gem, suitable for development with Bundler -
bundle platform(1)
: Display platform compatibility information -
bundle clean(1)
: Clean up unused gems in your Bundler directory -
bundle doctor(1)
: Display warnings about common problems -
bundle remove(1)
: Removes gems from the Gemfile
When running a command that isn't listed in PRIMARY COMMANDS or UTILITIES,
Bundler will try to find an executable on your path named bundler-<command>
and execute it, passing down any extra arguments to it.
These commands are obsolete and should no longer be used:
bundle cache(1)
bundle show(1)