Closed 927589452 closed 3 years ago
Can you name an example? The current supervisord sections (e.g. guide_etherpad.html#setup-daemon) contain tool-specific paths and the tool name in console output. Generalizing the config part makes it less copy-paste-able. Removing the tool name from console output might confuse reads, but sounds reasonable to reduce clutter.
exactly the latter would have been my suggestion the service name could be replaced with SERVICE leading to a more uniform snippet, as some tools split the parts and put more information into it (e.g. https://lab.uberspace.de/guide_postgresql.html?highlight=postgresql#setup-daemon) the first part is quite important, as a tool may need to be started on a special way like using the virtualenv's python
also the snippet (or maybe the manual https://manual.uberspace.de/daemons-supervisord.html#supervisord ) should hint at supervisord not sourcing any environment variable like the ones from .bash_rc and .bash_profile
supervisorctl reread/update/status
part with .. include:: includes/supervisord.rst
grep supervisord source/* | awk -F ':' '{print $1 }' | uniq
the most part for supervisord could be move into a snippet, except the supervisord unit