Thanks John,
#{rails_env} doesn't appear to be defined anywhere by default. It
throws an error when I try to use it in config/deploy.rb
On Tue, Jun 17, 2008 at 1:39 AM, John Ward <[EMAIL PROTECTED]> wrote:
> I have 2 instances of my application running on the same server. I use the
> mutistage plugin and have a staging, and production deploy file.
>
> The deploy's for each of the environments have dynamic vars which use the
> env to specify location of deployment and the mongrel conf to use
>
> set :deploy_to, "/var/www/#{application}_#{rails_env}" # defaults to
> "/u/apps/#{application}"
> set :mongrel_conf,
> "#{current_path}/config/deploy/#{rails_env}_mongrel_cluster.yml"
>
> This means that staging is deployed to
>
> /var/www/myapp_staging
>
> and production is deployed to
>
> /var/www/myapp_production
>
> Finally each environment has its own mongrel configuration, where you can
> set the number of mongrel instances and the ports to run on.
>
> "/var/www/myapp_staging/config/deploy/staging_mongrel_cluster.yml"
> "/var/www/myapp_staging/config/deploy/production_mongrel_cluster.yml"
>
> Outside of this you need to configure your front end load balancer. I have
> configured apache to work with 2 virtual hosts
>
> beta.myapp.com
> www.myapp.com
>
> The configuration of each individual vhost needs to proxy connections to the
> appropiate set of mongrels.
>
> On Tue, Jun 17, 2008 at 8:42 AM, Anthony Ettinger <[EMAIL PROTECTED]>
> wrote:
>>
>> How do I setup my server to handle both production and test environments?
>>
>> The only way I have found so far is to set RAILS_ENV = 'production' in
>> the .bashrc file
>>
>> --
>> Anthony Ettinger
>> 408-656-2473
>> http://anthony.ettinger.name
>>
>>
>
>
> >
>
--
Anthony Ettinger
408-656-2473
http://anthony.ettinger.name
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
