|
From: | Ludovic Courtès |
Subject: | Re: (Exposing?) config files and non-start/stop operations |
Date: | Sat, 26 Nov 2016 18:40:00 +0100 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Ricardo Wurmus <address@hidden> skribis: > Christopher Allan Webber <address@hidden> writes: > >> - We could also have a shepherd action like "herd config mediagoblin" >> that would merely spit out the configuration file path... so someone >> could do something like: >> $ foo-db dump-db --config `herd config foo-db` > > Here’s another similar idea: > > herd environment <service> -- some command > > The environment for a service may be represented by a bunch of > environment variables. “some command” then runs within this > environment and can access the variables. > > So if “foo-db” can read its configuration file from FOO_DB_CONFIG the > environment definition would be something like > > #~(("FOO_DB_CONFIG" . (string-append #$foo-db "/etc/config"))) Problem is that in many cases the config file is passed via a command-line option to the daemon. Ludo’.
[Prev in Thread] | Current Thread | [Next in Thread] |