On Tue, Dec 2, 2008 at 22:28, Dee Zsombor <[EMAIL PROTECTED]> wrote: > > I could say the contrary, on every project with a solid Mongrel or FCGI > based setup the spawner script was used. It requires no extra > configuration unlike monit/god/runit. It also cares for safely exiting a > process *after* the current request was processed unlike the defaults for > monit/god/runit etc. > > In what way did you find them to be broken?
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. Also, the limitation of these scripts compared to, say, mongrel_cluster was that you couldn't specify unix user/group for processes. Also, Koz likes Passenger very much and Rails is opinionated, remember? ;) j/k To conclude, I have nothing against this change, I just wanted to be sure why it was done. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
