Also, if you are using Capistrano to deploy, you can create targets
that setup the role definitions, so that you can also do deploys to
your staging environment. We have a half dozen different deploy
targets, and deploy by specifying the target, and
deploy/deploy_with_migrations, e.g.: "cap staging deploy"
One of the cap deployment target tasks simply looks like:
desc "Target the empqa cluster for remote operations"
task :empqa do
set :deploy_target, 'empqa'
set :db_server, 'empqa-07'
role :web, 'empqa-02', 'empqa-04'
role :app, 'empqa-02', 'empqa-04'
role :db, "#{db_server}", :primary => true
end
(Note that the "db_server" variable we set is so that we can generate
the proper database.yml.)
On 6/23/07, Andrew Semprebon <[EMAIL PROTECTED]> wrote:
> Make a copy the production.rb in config/environments/ and call it
> staging.rb, and add a new section to your database.yml called staging. This
> will give you a new environment called staging, which you then can modify as
> needed.
>
>
> On 6/23/07, Faisal N Jawdat <[EMAIL PROTECTED]> wrote:
> >
> > In Rails I have the development/test/production split, but...
> >
> > From an operational point of view I want a production server and a
> > staging server, with the staging server mirroring the setup of the
> > production server as much as possible so I can shake out issues that
> > are environment-specific.
> >
> > Any thoughts on how to do this or pointers to those who've already
> > done it?
> >
> > -faisal
> >
> >
> > > >
> >
>
--
Chris Bailey
[EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
