Adventures with Supervisord

Supervisord has a companion program "supervisorctl". Turns out that supervisord does not reread its configuration file unless you forcefully restart it. My initial thought was that it might be enough to change the configuration and then simply run a command like "supervisorctl restart instance1". Unfortunately my new settings were not detected.

(wasted nuff time...)

In the end I had to kill supervisord then restart it.

Reflecting on this, it does make sense, the role of supervisorctl is controlling and interfacing with supervisord, not to look behind its back for new settings.