>From my understanding, Gemfile.lock lists all the gems installed for the application along with the specific versions used. This means your app will only use the versions mentioned here and no others, even if updates for those gems are available. When you are deploying your application to staging or production, your application is going on a separate server so you want to make sure all the same versions of the gems are installed there as your local development system, so you should use bundle lock in this situation. So does that mean when you use capistrano to do a production deploy, and you always run bundle install during a deploy, should you run "bundle lock" before you run "bundle install" during the deploy process to production to make sure that gems aren't updated in production if they are not updated in development computer?
-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-talk@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
