Via the following script/spin.
-----------------
#!/usr/bin/env ruby
File.expand_path(File.dirname(__FILE__)).match(/var\/rails\/bwls\/([^\/]+)\//)
sitename = $1
ports = {
'bdea_demo' => [3110,1],
'bdea' => [3010,1],
'worldwide_demo' => [3120,1],
'worldwide' => [3030,3],
'brightwayslearning_demo' => [3130,1],
'raven' => [3060,1]
}
raise RuntimeError, "Site '#{sitename}' not setup in script/spin."
unless ports[sitename]
%x{#{File.dirname(__FILE__)}/process/spawner mongrel -p
#{ports[sitename][0]} -i #{ports[sitename][1]} -a 127.0.0.1}
---------------------
Jamis Buck wrote:
> How are you starting the mongrels?
>
> - Jamis
>
> On 8/2/07, Jon Garvin <[EMAIL PROTECTED]> wrote:
>
>> Ok, I've got our cap setup all converted to cap2 and simplified our old
>> recipes immensely in the process. Everything is SOOO much cleaner now.
>>
>> The one last problem that we've discovered is that when we redeploy a
>> site, OR just run deploy:restart, OR ssh directly to the server and from
>> app/current rails_root run script/process/reaper, mongrel gets
>> restarted, but it's still running from an OLD release directory, so it
>> doesn't have any new code. If we flat our kill the mongrel manually,
>> and then run script/spin, a new mongrel starts up pointed to the correct
>> release directory.
>>
>> Anybody got a clue/hint/bone to throw my way? Thanks.
>>
>> --
>> http://www.5valleys.com/
>>
>>
>>
>
> >
>
>
--
http://www.5valleys.com/
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
