On Feb 13, 2011, at 11:35 AM, Fernando Perez wrote: > As a side note question, should Gemfile.lock be added to the repository > and uploaded to the production server?
Generally it's not a good idea to include generated artifacts in a repository, but I do check my gemfile.lock in for a number of reasons. Firstly it's good documentation as it shows clearly in the commit log the gems, versions and dependencies (and you can easily see what new dependencies are introduced with each gem which can be useful). Also, my understanding is that in production mode, the --deployment flag should be used, and that required a gemfile.lock to ensure your production version is using the same versions that you tested in dev and production. Yehuda posted something on this: http://yehudakatz.com/2010/12/16/clarifying-the-roles-of-the-gemspec-and-gemfile/ The key is the third paragraph. Best Wishes, Peter > > -- > Posted via http://www.ruby-forum.com/. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
