Ricardo Wurmus skribis:
> Thompson, David writes:
>
>> I'm seeing a trend where people write services with configuration
>> types that don't cover nearly the amount of configuration options to
>> make the service useful. MySQL, and now this Redis
Am 13.01.2017 um 23:01 schrieb Ricardo Wurmus:
> We can extend them later as people see the need for better coverage.
> One thing I’d always like to see, though, is an escape hatch that allows
> users to extend the service with plain text configuration snippets.
+1
--
Regards
Hartmut Goebel
|
Thompson, David writes:
> I'm seeing a trend where people write services with configuration
> types that don't cover nearly the amount of configuration options to
> make the service useful. MySQL, and now this Redis server, are
> examples of this. There are many more
On Fri, Jan 13, 2017 at 09:22:01AM -0500, Thompson, David wrote:
I'm seeing a trend where people write services with configuration
types that don't cover nearly the amount of configuration options to
make the service useful. MySQL, and now this Redis server, are
examples of
Hi Dave,
Someone can always extend the configuration with more options, I don't
think that all options need to be exposed to make the service useful.
I don't think we should hold up patches that can easily be extended later
and don't break anything.
David
Hello,
On Tue, Jan 10, 2017 at 2:24 AM, Christopher Baines wrote:
>
> diff --git a/gnu/services/databases.scm b/gnu/services/databases.scm
> index d88c839f7..b6bdd6080 100644
> --- a/gnu/services/databases.scm
> +++ b/gnu/services/databases.scm
> @@ -35,7 +35,11 @@
>
Hi,
Christopher Baines skribis:
> * gnu/services/database.scm (): New record type.
> (%redis-accounts, redis-service-type): New variables.
> (default-redis.conf, redis-activation, redis-shepherd-service): New
> procedures.
> * doc/guix.texi (Database Services): Document the