Re: (Exposing?) config files and non-start/stop operations

[Ludovic Courtès]

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’.