Tag Info

New answers tagged

0

No, it's not possible to customize behaviour of Supervisor when it receives signal(s), without changing source code and adding that ability. Only thing you can do is specify is the kill signal for the process when it is going to be stopped, via "stopsignal" option.


0

I was able to do this by adding this to my nginx configuration file: upstream supervisor { server 127.0.0.1:9001 fail_timeout=0; } server { # server configuration location /supervisor { return 301 $uri/index.html; } location /supervisor/ { proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; # hack the host ...


2

This feature has been added to Supervisor recently environment=PATH="/home/site/environments/master/bin:%(ENV_PATH)s" https://github.com/Supervisor/supervisor/blob/master/supervisor/skel/sample.conf#L8 See also https://stackoverflow.com/questions/12900402/supervisor-and-environment-variables


2

There is no way to specify interval in supervisor program section, but what you could do is put "sleep()" into your code so that after program waits for specified period of time after it finishes with message processing. If you don't want/cant alter the program code, you may try wrapping it into bash script, for example: #!/bin/bash ...


3

That's the whole idea, to use systemd (or upstart etc) inside a container. Docker is used most of the time to run a single service per container, so for a complex site you would need a container for the web server and another one for the database server. With a process manager you could run both in the same container. Which approach is better is ...



Top 50 recent answers are included