unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] services: nginx: Allow for server extensions.
Date: Wed, 02 Dec 2015 10:07:23 +0200	[thread overview]
Message-ID: <87r3j51dfo.fsf@gnu.org> (raw)
In-Reply-To: <874mg2tg7s.fsf@izanagi.i-did-not-set--mail-host-address--so-tickle-me> (David Thompson's message of "Tue, 01 Dec 2015 09:07:35 -0500")

David Thompson <dthompson2@worcester.edu> skribis:

> Looking for some feedback on my first stab at making the nginx service
> extensible.  With this extension mechanism, future web applications
> (such as GNU MediaGoblin) that use nginx as a front-end web server will
> be able to extend nginx with the server configuration that they need in
> order to work.

Excellent!

> Here's a useless service that adds nginx configuration to serve the
> contents of /tmp:
>
>     (define server
>       (plain-file "foo.conf"
>                   "
>     server {
>       listen 80;
>       root /tmp;
>       index index.html;
>       server_name dthompson.us;
>     }
>     "))

Do you think it would make sense to provide Scheme bindings for those
‘server’ configuration snippets, or would we lose too much
expressiveness?

> From 108db2d183526c42b53060e55f7fb292b53663cb Mon Sep 17 00:00:00 2001
> From: David Thompson <dthompson2@worcester.edu>
> Date: Mon, 30 Nov 2015 08:49:08 -0500
> Subject: [PATCH] services: nginx: Allow for server extensions.
>
> * gnu/services/web.scm (<nginx-configuration>)[servers]: New field.
>   (nginx-configuration-servers): New accessor.
>   (default-nginx-config): Delete.
>   (nginx-configuration-file*): New procedure.
>   (nginx-activation): Perform the syntax check on the full computed
>   configuration file.
>   (nginx-dmd-service): Use the full computed configuration file when
>   starting the service.
>   (extend-nginx): New procedure.
>   (nginx-service-type): Specify extension procedures.
>   (nginx-service): Add #:servers argument.

[...]

> +(define (nginx-configuration-file* config)

‘nginx-configuration->file’ maybe?

Otherwise LGTM!

As an exercise, and while waiting for Chris to finish packaging
MediaGoblin ;-), it might make sense to try to use nginx in
‘guix-publish-service’ or a variant thereof.

Thank you!

Ludo’.

  reply	other threads:[~2015-12-02 10:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 14:07 [PATCH] services: nginx: Allow for server extensions David Thompson
2015-12-02  8:07 ` Ludovic Courtès [this message]
2015-12-07 19:57   ` Leo Famulari
2015-12-07 23:06     ` Ludovic Courtès
2016-02-28 16:31   ` 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=87r3j51dfo.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dthompson2@worcester.edu \
    --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).