I have some question about the useability of the bundle and the generated configurations
Is it possible to generate only worker configuration as on my production and dev server I already have a supervirod.conf with other configuration needed for the project. So I can generate only the worker config and include them in my root supervisord.conf file.
Is it recommended to commit configuration or is it a better way to build it on deploy and restart supervisor ?
My application has two separate instances on my staging environement. For now I created two different supervisor groups (one for each application instance) to restart all programms for a given group instead of restarting supervisor completely. I found that the Supervisor service already have an execute method to execute supervisorctl commands. Is it only about creating new commands to restart supervisor programms/group ? And some options to only generate worker configurations ?
Hello !
I have some question about the useability of the bundle and the generated configurations
Is it possible to generate only worker configuration as on my production and dev server I already have a supervirod.conf with other configuration needed for the project. So I can generate only the worker config and include them in my root supervisord.conf file.
Is it recommended to commit configuration or is it a better way to build it on deploy and restart supervisor ?
My application has two separate instances on my staging environement. For now I created two different supervisor groups (one for each application instance) to restart all programms for a given group instead of restarting supervisor completely. I found that the
Supervisorservice already have anexecutemethod to executesupervisorctlcommands. Is it only about creating new commands to restart supervisor programms/group ? And some options to only generate worker configurations ?Thanks for your answer. Let me know if I can help