Whats the difference between bundle install --deployment and bundle pack

Question

I know they both put the gems in your app in different locations but it seems as if bundle install --deployment does a more thorough job. Can I just add the vendor/bundle directory it creates to version control and be done?

Answer 1

I use bundle install --path vendor/bundle in development mode. bundle install --deployment will lock yor Gemfile.lock and will not update it when you change your Gemfile, so never use deployment option on development environment. bundle install --no-deployment will disable bundle deployment mode. You can read that post about bundle usage in right way.

Answer 2

Have a look at the description of the two on Bundler's site.

Running bundle install --deployment is to be run in the production environment, but will grab the gems from rubygems when run. Read more here under the 'Deploying Your Application' heading for the purpose of the --deployment flag.

bundle package is similar to the old rake rails:gems:freeze command from Rails 2.3. It grabs the gems and packages them in vendor/cache. From the bundler site here:

You can use this to avoid a dependency on rubygems.org at deploy time, or if you have private gems that are not in a public repository

Answer 3

I explained the reasoning behind the --deployment mode flag at pretty great length in a talk I gave at RailsConf 2011. This blog post contains my notes for that talk, and (I hope) covers all of the reasoning behind the way --deployment works: http://andre.arko.net/2011/06/11/deploying-with-bundler-notes/