New answers tagged

0

Use sed to edit them all at the same time. sed -i -e 's/numprocs=3/numprocs=4/g' your_conf.conf or if using vi shift+V+G, shift+:+g/numprocs=3/s//numprocs=4/g Maybe it's not the direct answer but in management it's better to keep each [program:] block in separate file thing-one.conf, thing-two.conf, thing-three.conf. In case you would like to turn off one ...


0

I doubt this is what your looking for but depending on what your end goals are you could use a script to generate the config. I am a sys admin not a developer so excuse poor coding practices. But this would allow you to just add a single line to add a new app. If you wanted to change any of the existing directives you also would only have to do it once in ...


0

Since there are only three instances of the same program that differ only on one argument, we can employ Python's string expression expansion inside command like following. [program:things] command=/usr/local/thing --instance %(process_num)s numprocs=3 user=a_user stdout_logfile=/var/log/thing.log autostart=true autorestart=true startsecs=10 ...


1

Regarding your configuration, you can pass in compose environment variable using env_file for a file or environment directly: https://docs.docker.com/compose/compose-file/#env-file For the IP, when you link containers in Compose, the name of the container you set in your yml will be the hostname of this container. You don't need an IP, just the username. ...


0

runit is a successor to daemontools (both are written in c) supervisord uses python. I've been using runit with socklog by the same author inside Alpine Linux lxc containers for around 10 months to manage web / database & various other services. It is light, easy to manage & I have had no service failures. The logging daemon also runs as it's ...



Top 50 recent answers are included