|Sent on:||Thursday, October 4, 2012 2:36 PM|
On Thursday, October 4, 2012 at 2:31 PM, Kevin wrote:
Rubyists,I'm working at a formerly Java and now Java/Erlang(yay!)/Ruby shop w/o hiring any rails folks (I'm a rails 1.0/1.1 guy)... so our DBAs came along and created new databases in database.yml, set the RAILS_ENV to their new database and our off and running our apps without any config/environment so our apps our running in development mode (fun!)..So.... I was wondering.Do folks typically (#1) create a new environment for each server. E.g., RAILS_ENV=( atl-production, ny-production), etc and use one big database.yml (potentially)or (#2) deploy a rails app running RAILS_ENV=production, and tailor the database.yml production values for each location?And if the answer is (#2), how can I keep this proliferation of environments DRY?thanks- kb
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Kevin ([address removed]) from The Atlanta Ruby Meetup Group.
To learn more about Kevin, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]