Control Resque through Capistrano using systemd
Restarting a resque service using just a cap (Capistrano) command is handy and sometimes needed.
Instead of relying on Capistrano plugins like
capistrano-resque that spawn and
track worker processes themselves, we let systemd
supervise the Resque workers. systemd
takes care of restarting crashed workers, starting them on boot, and
collecting their logs through journalctl. Capistrano then only has to send
start, stop, and restart commands to the already configured service,
exactly the same way you would do it by hand on the server.