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.

=> http://cr.yp.to/redo.html

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

    $ redo fcgi.example.cmd
    # 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 make-update 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/example-update.sh web-server:/tmp
    web-server $ /tmp/example-update.sh /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.