unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: services: Add redis-service
Date: Sat, 14 Jan 2017 14:40:42 +0100	[thread overview]
Message-ID: <87bmv9pxnp.fsf@gnu.org> (raw)
In-Reply-To: <87h952liup.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 13 Jan 2017 23:01:50 +0100")

Ricardo Wurmus <rekado@elephly.net> skribis:

> Thompson, David <dthompson2@worcester.edu> 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 configuration options in Redis
>> than this service exposes.
>>
>> What do we do?
>
> Since there is no automated way to cover all options (or even the most
> useful subset) for all possible services I think it’s okay to start with
> a minimally useful service definition.
>
> 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.

Agreed.  I like it when people submit full-featured services, like the
OpenVPN services that were posted recently, but I think it’s also
valuable to have first stabs at services like this Redis server.  It
is functional and useful, lowers the barrier for the initial submitter
as well as for people who want to improve it.

Ludo’.

      parent reply	other threads:[~2017-01-14 13:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10  7:24 [PATCH] gnu: services: Add redis-service Christopher Baines
2017-01-12 15:49 ` Ludovic Courtès
2017-01-13 14:22 ` Thompson, David
2017-01-13 14:42   ` David Craven
2017-01-13 14:56   ` John Darrington
2017-01-13 22:01   ` Ricardo Wurmus
2017-01-14 10:37     ` Hartmut Goebel
2017-01-14 13:40     ` Ludovic Courtès [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bmv9pxnp.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).