I'm generating supervisor configuration files as well. Seems
perfectly reasonable. I use supervisorctl to reload the
configurations after I've created them. I stick all my generated
files in an include/ directory, and include it from a parent
supervisor config.
-- Philip
On Mon, Nov 29, 2010 a
The most useful one is %(here)s, which is expanded in most contexts.
See
http://supervisord.org/configuration.html#unix-http-server-section-values for
example.
On Mon, 2010-11-29 at 16:40 -0800, Yang Zhang wrote:
> Anyone?
>
> On Fri, Nov 12, 2010 at 12:57 AM, Yang Zhang wrote:
> > I'm buildin
Anyone?
On Fri, Nov 12, 2010 at 12:57 AM, Yang Zhang wrote:
> I'm building an application where I'd like to use supervisord.
> However, I'd like to avoid hard-coding paths and other parameters used
> by supervisord into a static config file (most of the parameters come
> from a combination of com
I'm building an application where I'd like to use supervisord.
However, I'd like to avoid hard-coding paths and other parameters used
by supervisord into a static config file (most of the parameters come
from a combination of command-line tools and configuration files
belonging to the application).
