On Saturday, April 27, 2013 6:20:40 PM UTC+1, John Merlino wrote: > 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?
Bundle lock was deprecated something like 3 years ago. Bundle install does it for you Fred -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/3e7c_ONaWXkJ. For more options, visit https://groups.google.com/groups/opt_out.
