BUNDLE(1)BUNDLE(1)NAME
bundle - Ruby Dependency Management
SYNOPSIS
bundle COMMAND [--no-color] [--verbose] [ARGS]
DESCRIPTION
Bundler manages an application's dependencies through its entire life across many machines systematically and repeatably.
See the bundler website http://gembundler.com for information on getting started, and Gemfile(5) for more information on the Gemfile for-
mat.
OPTIONS --no-color
Prints all output without color
--verbose
Prints out additional logging information
BUNDLE COMMANDS
We divide bundle subcommands into primary commands and utilities.
PRIMARY COMMANDS
bundle install(1) bundle-install.1.html
Install the gems specified by the Gemfile or Gemfile.lock
bundle update(1) bundle-update.1.html
Update dependencies to their latest versions
bundle package(1) bundle-package.1.html
Package the .gem files required by your application into the vendor/cache directory
bundle exec(1) bundle-exec.1.html
Execute a script in the context of the current bundle
bundle config(1) bundle-config.1.html
Specify and read configuration options for bundler
UTILITIES
bundle check(1)
Determine whether the requirements for your application are installed and available to bundler
bundle list(1)
Show all of the gems in the current bundle
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 context of the current bundle
bundle open(1)
Open an installed gem in the editor
bundle viz(1)
Generate a visual representation of your dependencies
bundle init(1)
Generate a simple Gemfile, placed in the current directory
bundle gem(1)
Create a simple gem, suitable for development with bundler
OBSOLETE
These commands are obsolete and should no longer be used
o bundle lock(1)
o bundle unlock(1)
o bundle cache(1)
June 2012 BUNDLE(1)
Check Out this Related Man Page
BUNDLE-PACKAGE(1)BUNDLE-PACKAGE(1)NAME
bundle-package - Package your needed .gem files into your application
SYNOPSIS
bundle package
DESCRIPTION
Copy 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.1.html, use the gems in the cache in preference to the ones on rubygems.org.
GIT AND PATH GEMS
In Bundler 1.0, the bundle package command only packages .gem files, not gems specified using the :git or :path options. This will likely
change in the future.
REMOTE FETCHING
By default, if you simply run bundle install(1) bundle-install.1.html after running bundle package(1) bundle-package.1.html, bundler will
still connect to rubygems.org to check whether a platform-specific gem exists for any of the gems in vendor/cache.
For instance, consider this Gemfile(5):
source "http://rubygems.org"
gem "nokogiri"
If you run bundle package under C Ruby, bundler will retrieve the version of nokogiri for the "ruby" platform. If you deploy to JRuby and
run bundle install, bundler is forced to check to see whether a "java" platformed nokogiri exists.
Even though the nokogiri gem for the Ruby platform is technically acceptable on JRuby, it actually has a C extension that does not run on
JRuby. As a result, bundler will, by default, still connect to rubygems.org to check whether it has a version of one of your gems more spe-
cific to your platform.
This problem is also not just limited to the "java" platform. A similar (common) problem can happen when developing on Windows and deploy-
ing to Linux, or even when developing on OSX and deploying to Linux.
If you know for sure that the gems packaged in vendor/cache are appropriate for the platform you are on, you can run bundle install --local
to skip checking for more appropriate gems, and just use the ones in vendor/cache.
One way to be sure that you have the right platformed versions of all your gems is to run bundle package on an identical machine and check
in the gems. For instance, you can run bundle package on an identical staging box during your staging process, and check in the ven-
dor/cache before deploying to production.
June 2012 BUNDLE-PACKAGE(1)