Hello,
I'm using a configuration management tool (Salt) to create entries in
/etc/supervisor/conf.d for various applications.
I'm running supervisor v3.0b2.
It's logical for each application to have its own config file, to
simplify generation, deployment and management of the files.
The problem is, I want multiple files to have programs in the same
'group', like this:
#/etc/supervisor/conf.d/audio.conf
[group:workers]
programs=audioworker
[program:audioworker]
# blah blah blah
And:
#/etc/supervisor/conf.d/video.conf
[group:workers]
programs=videoworker
[program:videoworker]
# blah blah blah
This doesn't work - only one of the programs ends up in the 'worker'
group, with the other one put into a group named for itself, per the
default.
Is there some way around this without each program having to know about
the other programs in its config file, and without having a single
shared file for each config?
If not, is there be any opposition to a patch that provides for this?
Cheers,
Daniel
_______________________________________________
Supervisor-users mailing list
[email protected]
https://lists.supervisord.org/mailman/listinfo/supervisor-users
