process/reaper should work fine with mongrel_rails. Just make sure mongrel_rails writes it's pid file to tmp/pids (which ought to be a symlink pointing to the shared directory somewhere). You might still need to override deploy:stop and deploy:restart, to pass the necessary parameters to the reaper (so it knows what the names of the pid files are).
- Jamis On 8/7/07, Graham Ashton <[EMAIL PROTECTED]> wrote: > > On 03/08/07, Jamis Buck <[EMAIL PROTECTED]> wrote: > > > > The "spin" script is described here: > > > > http://www.capify.org/getting-started/rails > > > > (Search the page for "spin".) Basically, all it is, is a shell script > > that contains the calls needed to start up your listeners, be they > > fcgi or mongrel. If you're using mongrel cluster, you might put the > > necessary mongrel cluster calls there. > > Whilst upgrading to cap2 I've been trying to step away from > mongrel_cluster, in favour of script/process/spawner and reaper. > However, I have a slightly irksome problem. > > I need to set ActionController::AbstractRequest.relative_url_root so > that my entire app is served up from '/foo', and I can't find anyway > to do this with script/process/spawner. You can set the prefix with > the --prefix option to mongrel_rails. > > I may end up having to put a call to mongrel_rails in script/spin, but > if I do that, how would you recommend stopping/restarting the servers? > I'm thinking of overwriting deploy:stop, but wondered if there was a > cleaner way... > > Cheers, > > Graham > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
