Raul wrote: > You know I had the same problem. I'm no Linux guru so I'll just explain > to > the best of my ability how I overcame it. > > I'm running Centos (Redhat) so I needed to set up the service so that my > mongrel_cluster will autostart my mongrels. I just made sure the symlink > in > the init.d folder on the production servers points to my production yml > file > since when I deploy it pushes both development and production yml files. > > I don't know if that helps but after trying a bunch of stuff with the > app > configs and not being able to get it working I gave up and approached it > from outside the application and it works like a charm.
Thanks, Raul. For the time being I've backed off to using a single mongrel instance rather than a cluster, but that's not ideal for production, and will only become less and less so as traffic increases. At the moment I have both staging and production environments running on the same box, but I could probably arrange something like this as they're obviously in completely separate directories. I can't believe I'm unique in experiencing this. Anyone else? -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 -~----------~----~----~----~------~----~------~--~---
