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 at 4:40 PM, Yang Zhang <[email protected]> wrote: > Anyone? > > On Fri, Nov 12, 2010 at 12:57 AM, Yang Zhang <[email protected]> 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 command-line tools and configuration files >> belonging to the application). As a result, I'm just generating >> supervisord configuration files. Feels like a big hack for something >> that should be pretty common, so I figured I'd ask here to see if >> there's a Better Way. Thanks in advance for any hints. >> -- >> Yang Zhang >> http://yz.mit.edu/ >> > > > > -- > Yang Zhang > http://yz.mit.edu/ > _______________________________________________ > Supervisor-users mailing list > [email protected] > http://lists.supervisord.org/mailman/listinfo/supervisor-users > _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
