From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Service refactoring
Date: Sat, 26 Sep 2015 14:50:31 +0200 [thread overview]
Message-ID: <874mih5oq0.fsf@gnu.org> (raw)
In-Reply-To: <87mvwartuq.fsf@dustycloud.org> (Christopher Allan Webber's message of "Fri, 25 Sep 2015 17:50:36 -0500")
Christopher Allan Webber <cwebber@dustycloud.org> skribis:
> So, nginx and apache have pretty drastically different config file
> types. However, most of the things users want I think are compatible
> with both. We probably want a "minimal" service that just accepts
> whatever config files for apache and nginx, and just lets the user
> specify that whole manually. We can have more advanced procedures for
> building up a config file by translating our world-of-s-expressions or
> whatever schemey types into the config file format... but given "just
> how much" you can do with nginx and apache that is just so wildly
> different between the two, we probably want something that provides an
> abastract representation of what most web applications need, some sort
> of "medium common denominator" (I don't think we need to shoot for
> lowest here!). That way we can have a general way of letting
> applications specify what they need from their web server, but also
> allow a sysadmin to go "full on manual" if they need to with the config
> file formats.
>
> Dave / Ludo: Does that fit with what you two are thinking as well?
Yes, sounds good. We just need to figure out what that common
denominator is. :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-09-26 12:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 21:23 [PATCHES] Get elogind-service working as intended Mark H Weaver
2015-09-04 7:57 ` Andy Wingo
2015-09-06 21:23 ` Service refactoring Ludovic Courtès
2015-09-08 8:47 ` Andy Wingo
2015-09-08 10:12 ` Ludovic Courtès
2015-09-08 10:33 ` Andy Wingo
2015-09-08 14:48 ` Mark H Weaver
2015-09-10 16:05 ` Ludovic Courtès
2015-09-10 16:14 ` Ludovic Courtès
2015-09-20 15:42 ` Ludovic Courtès
2015-09-21 8:18 ` Andy Wingo
2015-09-21 16:00 ` Ludovic Courtès
2015-09-24 0:33 ` Thompson, David
2015-09-24 7:41 ` Ludovic Courtès
2015-09-24 9:33 ` 宋文武
2015-09-24 17:09 ` Ludovic Courtès
2015-09-25 22:50 ` Christopher Allan Webber
2015-09-26 12:50 ` Ludovic Courtès [this message]
2015-09-30 8:59 ` Ludovic Courtès
2015-10-10 21:01 ` Ludovic Courtès
2015-09-10 16:03 ` [PATCHES] Get elogind-service working as intended Ludovic Courtès
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=874mih5oq0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cwebber@dustycloud.org \
--cc=guix-devel@gnu.org \
/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).