I concur... my supervisor.conf files are so large that I generate them from a template fed from a database table. With such a change, plus other recent improvements in accessing environment variable names, my supervisor.conf files could shrink by probably 70-80%.
tlj From: [email protected] [mailto:[email protected]] On Behalf Of Roger Hoover Sent: Wednesday, April 11, 2012 4:49 PM To: Steve Romanow Cc: [email protected] Subject: Re: [Supervisor-users] [group:] defaults I like it. It would shrink my config. On Wed, Apr 11, 2012 at 1:24 PM, Steve Romanow <[email protected]<mailto:[email protected]>> wrote: What do you guys think of this. Should all config keys that are valid for a [program:] entry also be valid for a [group:] entry and then you can just put the differences in the accompanying [program:] sections. I am think about a service there the only difference between the two jobs in the group are the paths in the directory key. Well, also the log name, but that can be abstracted with string substitution. _______________________________________________ Supervisor-users mailing list [email protected]<mailto:[email protected]> http://lists.supervisord.org/mailman/listinfo/supervisor-users
_______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
