Previous: , Up: godlighty  


All configuration is assumed to be placed in rc/cfg. Probably you want to deal with multiple server configurations simultaneously. You place them in corresponding rc/NAME.cfg directories and use redo default target to create necessary symbolic link of rc/NAME.cfg to rc/cfg and build executable itself.

$ redo example
# will produce example executable with rc/example.cfg configuration

$ redo fcgi.example
# will produce fcgi.example executable with rc/fcgi.example.cfg configuration

But because you will mostly like to create binary patches to quickly update already existing binaries, then you can use script, that will store newly created binaries in updates/ directory and make shell-script with the built-in binary patch and SHA512 checksum checker:

# First run
$ ./make-update example
$ scp updates/example.old web-server:/path/to/www-server

$ ./make-update example
$ scp updates/ web-server:/tmp
web-server $ /tmp/ /path/to/www-server
web-server $ svc -t /var/service/www-server

contrib/service contains daemontools example run scripts.

Send SIGINFO (SIGUSR1 on Linux) signal to get current daemon’s configuration.