Hmm, I hadn't realised it was that easy to create new environments. Thanks.
On Aug 17, 5:21 pm, "Alex Grigorovich" <[EMAIL PROTECTED]> wrote: > On 8/17/07, Drinkingbird <[EMAIL PROTECTED]> wrote: > > > I'm using the cap extension outlined > > athttp://weblog.jamisbuck.org/2007/7/23/capistrano-multistage > > to deploy to either staging or production environments. > > > The staging and production deployments are both on the same database, > > so when set to the same environment (in this case production), they > > both refer to the same database. > > > Since it's not practical for me to have the staging release run in > > development mode, can anyone recommend a good way to switch the > > configuration to a different database? > > Create a new "staging" section in config/database.yml, copy > config/environments/production.rb to config/environments/staging.rb > and put a line containing > > set :rails_env, "staging" > > in config/deploy/staging.rb. > > -- > Alex --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
