On Friday, April 13, 2012 at 1:34 PM, Rodrigo Rosenfeld Rosas wrote: > Em 13-04-2012 17:30, Josh Susser escreveu: > > The best way to set up a staging server is for it to be configured as > > close to production as possible, so I always run my staging server > > using the production.rb environment. If there are differences (like > > which S3 bucket to use), I put them in ENV settings or in files that > > aren't under version control. > > > > > That way you'd need an extra backup (aside from your git repository) for > storing each environment data, unless you're using something like > Capistrano or Chef. But setting up such environments when you're > starting your application may seem like overkill. > >
Storing server configuration in your app's git repo is not ideal. Chef recipes are much better. And if you're at the point where you need a staging server, you're definitely at the point where you should be using automation for managing your servers. How else will you know that your staging server accurately reflects the production configuration? You can go a long time without a staging server - often much longer than you can without configuration automation. And yes, you should store those recipes in version control. Just not in the app's repo. There are tons of reasons for keeping those things separate (security, decoupling, etc.) -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en.
