From: Leo Prikler <leo.prikler@student.tugraz.at>
To: raingloom <raingloom@riseup.net>,
"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Sharing system users for related services
Date: Mon, 22 Mar 2021 17:13:36 +0100 [thread overview]
Message-ID: <4a05774724102f08a936ddab509830ef48f4b8a5.camel@student.tugraz.at> (raw)
In-Reply-To: <20210322134006.4cd9f6dc@riseup.net>
Hi raingloom,
Am Montag, den 22.03.2021, 13:40 +0100 schrieb raingloom:
> I'm packaging the Molly Brown Gemini server and I'm trying to play
> nice
> with the already packaged gmnisrv.
> Should the two use the same service name and system users? Most users
> probably won't want to run both servers at the same time, so the
> former
> seems like a good idea. And the latter would be preferable because if
> they use the same certs, %gmnisrv-activation will trample over the
> permissions when they do want to run both for some reason.
>
> So should I just reuse %gmnisrv-accounts or should they both use a
> shared %gemini-server-accounts?
As the one, who wrote the code, that lets you share accounts as list
"pointers" in the first place, I do think something along the lines of
(define %molly-brown-accounts %gmnisrv-accounts)
with an appropriate comment should be fine, especially for a proof of
concept implementation. That being said, patch review is an ideal
opportunity to bikeshed such definitions ;)
Regards,
Leo
prev parent reply other threads:[~2021-03-22 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 12:40 Sharing system users for related services raingloom
2021-03-22 16:13 ` Leo Prikler [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=4a05774724102f08a936ddab509830ef48f4b8a5.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=guix-devel@gnu.org \
--cc=raingloom@riseup.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).