addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramlinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

[ruby-83] Rails Environment Question

From: Kevin
Sent on: Thursday, October 4, 2012 2:31 PM
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




Our Sponsors

  • Mailchimp

    Sponsors food, meeting space, and other expenses.

  • Pardot

    Sponsors food, meeting space, and other expenses.

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy