I'm deploying a rails app to separate production and staging
environments using Capistrano. They're basically running as two apps on
the same machine, so I want to make them available on different ports,
and may also want to have different numbers of mongrels in the clusters.
My plan was to build a config file name based on the RAILS_ENV setting -
something like ..../config/mongrel/staging.yml or
..../config/mongrel/production.yml and then set :mongrel_conf in the
deploy.rb so that the standard deployment recipes would pick it up. The
effect of that would be that they would run:
mongrel_rails cluster::start -C ..../config/mongrel/staging.yml
When I tried it it seemed to make no difference at all which config file
I specified, it would always try and start 2 mongrels on ports 3000 and
3001.
I tried running the mongrel_rails command on the server by hand and
exactly the same thing happened. Am I barking up the wrong tree?
mongrel_rails cluster::start -h seems to imply that this should work:
Usage: mongrel_rails <command> [options]
-C, --config PATH Path to cluster configuration file
-v, --verbose Print all called commands and
output.
-h, --help Show this message
--version Show version
Target platform is Ubuntu 7.04/Feisty, Mongrel 1.0.1, Ruby 1.8.5
-Chrisl
--
Posted via http://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
