Hi Willis:
Apologies if you get this twice. Google groups is timing out on me.
Dreamhost uses dynamic fcgi processes by default, so you shouldn't need
a spinner script. I belive their apache instance will fire a new fcgi
listener if a) one doesn't exist or b) there's a newer file on the
server. In short, you should only really need to run the setup action
and then the deploy action and things should 'just work'
However, I have the following tasks in my deploy files to deal with
problems I had with dreamhost:
desc "Remove the 'current' that dreamhost leaves lying around"
task :after_setup do
delete "#{current_path}", :recursive => true
end
desc "Restart the FCGI processes on the app server as a regular user."
task :restart, :roles => :app do
run "#{current_path}/script/process/reaper
--dispatcher=dispatch.fcgi"
end
I'm not sure if either, or both, are neccessary any more. They're in
my standard deploy.rb file, which has worked for many projects, but I
don't have time to investigate in more detail. I'd recommend trying
without both first then adding them to see if it helps.
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
