foreman-export-daemontools

home

bitbucket.org/ged/foreman-export-daemontools

github

github.com/ged/foreman-export-daemontools

docs

deveiate.org/code/foreman-export-daemontools

Description

An exporter for David Dollar’s Foreman that outputs service directories that can be managed by ‘supervise’ from DJB’s daemontools.

Prerequisites

Installation

$ gem install foreman-export-daemontools

Usage

To export your Procfile to the standard /service directory:

$ foreman export daemontools /service

This will create a /service/<app>-<proc> directory for each Procfile process. If you have the concurrency set to something > 1 for any of them it will create an individual numbered service directory for each one in the format: /service/<app>-<proc>-<num>

Each directory will be generated with a down file, which will prevent supervise from automatically starting it before you have a chance to look it over. After you confirm that everything looks okay, you can start them up just by removing down.

Contributing

You can check out the current development source with Mercurial from its main repository. Or if you prefer Git, via its Github mirror.

After checking out the source, run:

$ rake newb

This task will install any missing dependencies, run the tests/specs, and generate the API documentation.

License

Copyright © 2012, Michael Granger All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.