I push only one init.d script that's to start god. (you could use monit or bluepill too).
Then all of my apps dependencies involved in delivering our application get their own god configs pushed; then god is started. If a machine reboots; god gets started; then god takes over and starts everything else, keeps it running, and alerts when there are failures. Look at the god, nginx_unicorn, and unicorn recipes here as examples https://github.com/donnoman/cap-recipes/tree/master/lib/cap_recipes/tasks You'll also notice that by default each recipe can push its own init script, by changing the watcher you can enable god control; in the same way I left it open to create other watcher types; On Apr 18, 2012, at 11:31 AM, Bráulio Bhavamitra <[email protected]> wrote: > Hello all, > > I would like to know the best practices and references to > servers start on boot. > > Even with high uptime servers, we need to certify that server(s) > are running after a reboot, so this is necessary... > > I saw some just copying scripts to /etc/init.d and activating them. > But I would like to know more... > > Thankfully, > bráulio > -- > * You received this message because you are subscribed to the Google Groups > "Capistrano" 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/capistrano?hl=en -- * You received this message because you are subscribed to the Google Groups "Capistrano" 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/capistrano?hl=en
