From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 50882@debbugs.gnu.org, jgart <jgart@dismail.de>
Subject: [bug#50882] [PATCH] gnu: services: Add darkhttpd service
Date: Thu, 07 Jul 2022 14:02:36 -0400 [thread overview]
Message-ID: <87k08oztqb.fsf_-_@gmail.com> (raw)
In-Reply-To: <87bl3dl1xy.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Mon, 25 Oct 2021 14:32:41 +0200")
tag 50882 moreinfo
thanks
Hello jgart,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> jgart <jgart@dismail.de> skribis:
>
>> * gnu/services/web.scm (<darkhttpd-configuration>): New record type.
>> (darkhttpd-accounts, darkhttpd-shepherd-service): New procedures.
>> (darkhttpd-service-type): New variable.
>> * doc/guix.texi (Web Services): Adds documentation for darkhttpd.
>
> Overall LGTM! Some comments and suggestions below.
>
>> +@cindex darkhttpd
>> +@uref{https://unix4lyfe.org/darkhttpd/, darkhttpd} is a web server with a
>> +focus on security and having a small memory footprint.
>> +
>> +Some security features are the following:
>> +
>> +@itemize
>> +@item Logging accesses, including Referer and User-Agent.
>> +@item Can chroot.
>> +@item Can drop privileges.
>> +@item Impervious to /../ sniffing.
>> +@item Times out idle connections.
>> +@item Drops overly long requests.
>> +@end itemize
>
> I’d replace the bullet list with a simple sentence like: “Among other
> things, it can change root directories, drop privileges, it times out on
> idle connections and can drop overly long requests.”
>
>> +@deffn {Scheme Variable} darkhttpd-service-type
>> +This is the type of the darkhttpd service, whose value should be a
>> +@code{darkhttpd-service-type} object, as in this example:
>> +
>> +@lisp
>> +(service darkhttpd-service-type
>> + (darkhttpd-configuration
>
> Please don’t use tabs.
>
>> +@end table
>> +@end deftp
>> @node Certificate Services
>
> Missing newline before @node. :-)
>
>> + (mimetypes darkhttpd-configuration-mimetypes
>> + (default #f))
>> + (default-mimetype darkhttpd-configuration-default-mimetype
>
> Rather ‘mime-type’ (two words).
>
>> +(define darkhttpd-shepherd-service
>> + (match-lambda
>> + (($ <darkhttpd-configuration> package content port address
>> + maximum-connections log-file chroot?
>> + daemonize? index-file do-not-serve-listing?
>> + mimetypes default-mimetype
>> + drop-user-priviledges drop-group-priviledges
>> + write-pid-file disable-keep-alive?
>> + forward forward-all
>> + no-server-id? enable-ipv6?
>> + user group)
>
> Rather use ‘match-record’ here, to make sure we’re getting the right
> fields.
>
>> +(define darkhttpd-accounts
>> + (match-lambda
>> + (($ <darkhttpd-configuration> _ _ _ _ _ _ _ _
>> + _ _ _ _ _ _ _ _
>> + _ _ user group)
>
> In such a case, simply call ‘darkhttpd-configuration-user’ and
> ‘darkhttpd-configuration-group’; it’s much less error-prone!
>
>> +(define darkhttpd-service-type
>> + (service-type
>> + (name 'guix)
>> + (extensions
>> + (list (service-extension account-service-type
>> + darkhttpd-accounts)
>> + (service-extension shepherd-root-service-type
>> + darkhttpd-shepherd-service)))
>> + (default-value (darkhttpd-configuration))))
>
> Please add a ‘description’ field.
>
> Could you also add a system test, under (gnu tests web)? You can start
> by copying the nginx test; it should take around ~20 lines.
Friendly ping about the above requests from Ludovic :-).
Thanks,
Maxim
next prev parent reply other threads:[~2022-07-07 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 0:38 [bug#50882] [PATCH] gnu: services: Add darkhttpd service jgart via Guix-patches via
2021-09-29 0:46 ` [bug#50882] [PATCH] " jgart via Guix-patches via
2021-10-25 12:32 ` [bug#50882] [PATCH] gnu: " Ludovic Courtès
2022-07-07 18:02 ` Maxim Cournoyer [this message]
2022-07-08 0:20 ` jgart via Guix-patches via
2022-07-09 1:41 ` bug#50882: " Maxim Cournoyer
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=87k08oztqb.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=50882@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=ludo@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).