-
-
Notifications
You must be signed in to change notification settings - Fork 645
Replace daemonize with supervisord #1400
Comments
Daemonize is only used for Mailhog... but yeah, using Supervisord may be a bit simpler. Funny story, I just spent a couple weeks getting deeply familiar with Supervisord for some Docker internal service organization on a different project :) So I'm definitely +1 here, but the main thing would be adding a role, which I've been meaning to do anyways. Then after that, ensuring Mailhog runs under Supervisord instead of Daemonize. Which is pretty simple! |
Working on the role here: https://github.com/geerlingguy/ansible-role-supervisor Will need to play around with how I use the role to manage programs (or maybe delegate that task to the Mailhog role, and either make it work with either daemonize or supervisor, or make it just work with supervisor). |
It's actually fairly easy to get this working, now that I've had a little time to suss out the role. I don't know if I'll be able to get it into Drupal VM within the next few days, but this has some priority—it will also help with some more of the future Dockerization. |
Role is now working, documented, and feature-complete. |
I just reviewed the docs. This is looking good. |
Someday I'll get time to do this :P |
Someday... |
Issue Type
Summary
When recently setting up a queuing solution for Symfony, the suggested solution for daemonizing things was supervisord. And I find that installing it on Mac and Linux is fairly trivial. While installing daemonize on Linux is not so easy. It has to be installed from source. Which means that supervisor is much more popular. Why not switch to using it instead of daemonize? Then I can use supervisor in drupalvm and in my server environments too.
http://supervisord.org/installing.html
The text was updated successfully, but these errors were encountered: