Github user rnewson commented on a diff in the pull request:
    --- Diff: src/install/unix.rst ---
    @@ -229,10 +233,66 @@ CouchDB no longer ships with any daemonization 
     The couchdb team recommends `runit <>`_ to
     run CouchDB persistently and reliably. Configuration of runit is
    -straightforward; if you have questions, reach out to the CouchDB
    -user mailing list.
    +straightforward; if you have questions, contact the CouchDB
    +`user mailing list 
    +or `IRC-channel #couchdb <>`_
    +in FreeNode network.
    +Let's consider configuring runit on Ubuntu 16.04. The following
    +steps should be considered only as an example. Details will vary
    +by operating system and distribution. Check your system's package
    +management tools for specifics.
    +Install ruinit::
    +    sudo apt-get install runit
    +Create a directory where logs will be written::
    +    sudo mkdir /var/log/couchdb
    +    sudo chown couchdb:couchdb /var/log/couchdb
    +Create directories that will contain runit configuration for CouchDB::
    +    sudo mkdir /etc/sv/couchdb
    +    sudo mkdir /etc/sv/couchdb/log
    +Create /etc/sv/couchdb/log/run script::
    +    #!/bin/sh
    +    exec svlogd -tt /var/log/couchdb
    +Basically it determines where and how exactly logs will be written.
    +See ``man svlogd`` for more details.
    +Create /etc/sv/couchdb/run::
    +    #!/bin/sh
    +    export HOME=/home/couchdb
    +    exec 2>&1
    +    exec chpst -u couchdb /home/couchdb/bin/couchdb
    +This script determines how exactly CouchDB will be launched.
    +Feel free to add any additional arguments and environment
    +variables here if necessary.
    +Make scripts executable::
    +    sudo chmod u+x /etc/sv/couchdb/log/run
    +    sudo chmod u+x /etc/sv/couchdb/run
    +Then run::
    +    sudo ln -s /etc/sv/couchdb/ /etc/service/couchdb
    +In a few seconds runit will discover a new symlink and start CouchDB. You 
can control CouchDB service like this::
    +    sudo sv status couchdb
    +    sudo sv stop couchdb
    +    sudo sv start couchdb
    -Naturally, you can configure systemd, launchd or SysV-init daemons to
    -launch CouchDB and keep it running using standard configuration files.
    +Naturally now CouchDB will start autamatically shortly after system starts.
    --- End diff --
    typo 'autamatically' -> 'automatically'

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to