Bundler: The best way to manage a Ruby application's gems

Make sure all dependencies in your Gemfile are available to your application.

$ bundle install [--system]

Gems will be installed to your default system location for gems. If your system gems are stored in a root-owned location (such as in Mac OSX), bundle will ask for your root password to install them there.

While installing gems, Bundler will check vendor/cache and then your system's gems. If a gem isn't cached or installed, Bundler will try to install it from the sources you have declared in your Gemfile.

The --system option is the default. Pass it to switch back after using the --path option as described below.

Install your dependencies, even gems that are already installed to your system gems, to a location other than your system's gem repository. In this case, install them to vendor/bundle.

$ bundle install --path vendor/bundle

Further bundle commands or calls to Bundler.setup or Bundler.require will remember this location.

Learn More: Bundler.setup Learn More: Bundler.require

Install all dependencies except those in groups that are explicitly excluded.

$ bundle install --without development test

Learn More: Groups

Install all dependencies on to a production server. Do not use this flag on a development machine.

$ bundle install --deployment

The --deployment flag activates a number of deployment-friendly conventions:

Isolate all gems into vendor/bundle
Require an up-to-date Gemfile.lock
If bundle package was run, do not fetch gems from rubygems.org. Instead, only use gems in the checked in vendor/cache

Learn More: Deploying