In your deploy.rb you should have something like this: require 'capistrano/ext/multistage' set :stages, %w(production staging) set :default_stage, ""
Then when you call capistrano: cap staging deploy Note: In :stages you should write the filename (without extension) of your deploy/*.rb files Jeff Pritchard escribió: > Hi, > I thought it would be easy to get a staging server working. I'm using > capistrano 2 and the ext gem. I already had everything working with > capistrano for a production deployment... > > I added this to my deploy.rb > require 'capistrano/ext/monitor' > require 'capistrano/ext/multistage' > > I created a /deploy/staging.rb > set :deploy_to, "/where-the-staging-stuff-goes" > set :rails_env, 'staging' > > I added a ":staging" section in my database.yml file which is the same > as production section but points to a different database > > Most of this is working. The deployment works and I can run the app at > the new location, but for some reason it continues to use the production > database rather than the staging one that I have pointed it to with the > staging section of my database.yml file. > > thanks for any words of wisdom on this. > > jp > -- Rafael Garcia Ortega --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
begin:vcard fn;quoted-printable:Rafael Garc=C3=ADa Ortega n;quoted-printable:Garc=C3=ADa Ortega;Rafael org:ASPgems S.L. email;internet:[EMAIL PROTECTED] tel;work:692686533 x-mozilla-html:FALSE url:http://www.aspgems.com version:2.1 end:vcard
