.. _supervisord-configure: ============================================= Configure supervisord (logging, pidfile, ...) ============================================= We handle all logging through Supervisord, so you will probably at least want to configure where we log to. You configure supervisord through your ``buildout.cfg``. Add a ``supervisor``-section, and tune the settings:: [supervisor] # The full path to the supervisord log directory. # Defaults to /path/to/devilrybuild/var/log/ # Note: This setting is added by our buildout-base.cfg, and not by the # supervisor buildout recipe. #logdir = # The pid file of supervisord. Defaults to # /path/to/devilrybuild/var/supervisord.pid #pidfile = # The maximum number of bytes that may be consumed by the activity log file # before it is rotated. Defaults to 50MB. #logfile-maxbytes = # The number of backups to keep around resulting from activity log file # rotation. Defaults to 30. #logfile-backups = # If supervisord is run as the root user, switch users to this UNIX user # account before doing any meaningful processing. This value has no effect if # supervisord is not run as root. supervisord-user = Rebuild the Supervisord config (output in ``parts/supervisor/supervisord.conf``):: $ bin/buildout And restart supervisord. See the `Buildout recipe `_ and the `Supervisord docs `_ for more details. .. _supervisord-initscript: Init script =========== The following init script works well. You need to adjust the ``DAEMON``-variable (`download <_static/supervisord>`_): .. literalinclude:: /_static/supervisord :language: bash Harden supervisord ================== The default configuration if for a dedicated server. Supervisorctl uses a password with the local Supervisord server, which needs to be a better password in a shared environment. This should not be a problem since it is madness to host Devilry on a shared host in any case, but if you need to harden Supervisord, refer to the docs linked above.