https://github.com/multani/jb.recipe.supervisor
Configure and install Supervisord from Buildout
https://github.com/multani/jb.recipe.supervisor
Last synced: 9 months ago
JSON representation
Configure and install Supervisord from Buildout
- Host: GitHub
- URL: https://github.com/multani/jb.recipe.supervisor
- Owner: multani
- Created: 2012-03-11T10:37:33.000Z (about 14 years ago)
- Default Branch: master
- Last Pushed: 2012-03-11T11:21:26.000Z (about 14 years ago)
- Last Synced: 2025-02-23T12:19:46.223Z (over 1 year ago)
- Language: Python
- Homepage: http://pypi.python.org/pypi/jb.recipe.supervisor
- Size: 89.8 KB
- Stars: 1
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.rst
- Changelog: CHANGES.rst
Awesome Lists containing this project
README
Introduction
============
This recipe installs and configure `supervisor`_ according to a configuration
file.
How to use?
===========
You can use by configuration your ``buildout.cfg`` configuration file like
this::
[buildout]
parts = supervisor
[supervisor]
recipe = jb.recipe.supervisor
configuration-file = supervisor-sample.conf
You can download a sample configuration file at
https://github.com/multani/jb.recipe.supervisor/raw/master/supervisord-sample.conf
Running Buildout with this configuration file will generate:
* a `supervisor`_ configuration file using the template from the
``configuration-file`` settings as shown above;
* ``bin/supervisord``, which is a script to run the `supervisor`_ daemon,
according to the content of the configuration file above ;
* ``bin/supervisorctl``, which is a script to run the `supervisor`_ client,
according to the content of the configuration file above.
Additional settings
===================
By default, the configuration file will end in
``parts/PART_NAME/supervisord.conf``, but you can change it by setting the
``output-dir`` in your configuration file::
[buildout]
parts = supervisor
[supervisor]
recipe = jb.recipe.supervisor
configuration-file = supervisor-sample.conf
output-dir = /foo/bar
# The configuration will end in /foo/bar/supervisord.conf
The configuration file is processed by `collective.recipe.template`_. It means
you can use Buildout variables inside your template, such as
``${buildout:parts-directory}``, ``${_buildout_section_name_}``, or any valid
settings. See
http://pypi.python.org/pypi/zc.buildout/1.5.2#variable-substitutions for more
informations.
Related projects
================
`collective.recipe.supervisor`_ is a similar project, but with a different
approach. I liked to be able to configure `supervisor`_ from Buildout but I
found the syntax used by `collective.recipe.supervisor`_ to be confusing and
really ad-hoc.
.. _supervisor: http://supervisord.org
.. _collective.recipe.template: http://pypi.python.org/pypi/collective.recipe.template
.. _collective.recipe.supervisor: http://pypi.python.org/pypi/collective.recipe.supervisor