This could be a nice idea although I wonder if operational groups won't necessarily match groups that share configuration. For example, you might have a group of daemons that do image processing so you might want to group those together so that they can all be started/stopped in a single command. However, as far as sharing configuration parameters, you might want to have different groups like all perl daemons have certain params (like environment=PERL5LIB=/blah) and another group for python daemons. Those two sets of groups wouldn't always match up.
Another way to accomplish your goal use a templating tool to generate your supervisord config and that tool can support common includes. I'm doing this using Perl Template Toolkit. Cheers, Roger On Thu, Dec 30, 2010 at 3:41 AM, László Monda <[email protected]> wrote: > Hi List, > > How about adding the attributes of the program section to the group > section, too. That could shorten the size of the config file > tremendously in various scenarios. Maybe not all attributes make > sense, but I guess most do. > > -- > László Monda <http://monda.hu> > _______________________________________________ > 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
