hmm, thanks for the update.  I may give the full path route a try and see if 
it will work.  Then I can remove my symlink hack and scrap any extraneous 
documentation for server setup!

Raul

----- Original Message ----- 
From: "Chrisl" <[EMAIL PROTECTED]>
To: "Deploying Rails" <rubyonrails-deployment@googlegroups.com>
Sent: Friday, June 29, 2007 2:05 AM
Subject: [Rails-deploy] Re: Mongrel & multiple config files


>
> On Jun 23, 7:32 am, Paul H <[EMAIL PROTECTED]> wrote:
>> >From the sound of it, I am having the same experience. I am running
>>
>> both a staging and production environment all on one server. I have a
>> mongrel cluster for each environment. What I am finding is that
>> Capistrano is deploying everything right and restarting the cluster
>> for either staging or production but for some reason only one rails
>> app is actually running at a time. Its getting old. I can make a
>> requyest from either staging or production and I see both of the
>> request in the production log. I am stumped.
>
> Y'know, I've just gone back to this and tried it again, and well, darn
> it, it works perfectly.
> The only thing that I've changed is that I've supplied the path to the
> config file in full, and
> not as a relative path. This is in the light of some problems I had
> elsewhere, when I assumed
> that Capistrano was running the remote processes in the deployment
> directory, but it turned
> out it was running them in /
>
> I was mulling this over as I was going to sleep last night (as one
> does) and wondered if that
> had been the root of my problems. Looks like it might have been.
>
> -Chrisl
>
>
> > 


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to