Mislav Marohnić wrote: > What Koz meant is that with Mongrels you always need a monitoring daemon > in production (otherwise you'll be miserable). Because the monitoring > software already knows how to start/stop/restart mongrels (because > you've configured it), it's best practice to simply use that for > managing Mongrels. We are using god in the company and now that these > scripts are gone, we're switching to managing deployments through god > because it kinda feels right.
Spawner *is a monitoring superb daemon*, as long as you start Mongrels as described in: http://capify.org/getting-started/from-the-beginning instead of relying on mongrel_rails. -- Company - http://primalgrasp.com Thoughts - http://deezsombor.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
