We're using Capistrano to deploy several Rails sites to our server and use script/process/spawner via script/spin to start up the mongrel processes for each. Everything works great... but there's one gap not yet addressed. When the server gets rebooted, there's nothing in place to clean out the old pid files and re-spin things up again. We knew this was something we needed to look at, but since the server had been up for 250+ days... we weren't to concerned... that was until the machine got rebooted yesterday. <sigh>
When we were on Cap 1.x, instead of script/spin we had special mongrel_cluster services defined in /etc/init.d that our deploy recipe stopped and started, and that were also automatically started by the server on reboot. I'm not sure how best to make that kind or process play nicely with script/spin though. So, I'm curious what other people do. Are those with critical apps specifically *not* using script/spin and manually creating service scripts and deployment recipes like we did before? For some reason, I doubt that. So, what's the community's preferred method for re-spinning on reboot. Thanks. -- http://www.5valleys.com/ http://www.workingwithrails.com/person/8078 --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
