5 ms·
highly recommend runit + monit. The beauty of runit is the ./run script is easy to run by hand to test. The beauty of monit is it can watch things like http url
by rubyrescue 14y ago
highly recommend runit + monit. The beauty of runit is the ./run script is easy to run by hand to test. The beauty of monit is it can watch things like http urls and ports, and if something goes wrong, monit executes sv down myservice; sv up myservice. (sv is the actual launcher-thingy of runit)
If you use monit without runit, you end up in this weird world where monit starts and stops things in a very odd environment and it's flakier, environment variables are missing, etc. Also monit takes a long time to notice things are down, and doesn't start things right away on boot.
Finally if you don't boot your services with monit, you booted them with something else meaning that when a restart occurs, you're starting a service in a different environment than you booted in. weird.
so, let monit check health of things, let runit start and stop things.
- sandGorgon 14y agoare you using ruby with rhnit? which server (mongrel, thin, etc) do you recommend for playing nice with runit - which the OP mentioned has a problem with fork.
- rubyrescue 14y agopassenger