all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, quiliro@riseup.net
Subject: Re: personal communications server
Date: Wed, 07 Aug 2019 09:00:41 +0200	[thread overview]
Message-ID: <B61F8332-FCB8-48CC-AE13-5CCA9F94B820@lepiller.eu> (raw)
In-Reply-To: <6c155c97ee82a33f962788b887cda397.squirrel@sm.riseup.net>

Le 6 août 2019 23:48:29 GMT+02:00, quiliro@riseup.net a écrit :
>> I don't think we need the bash scripts, only services. From what I
>read,
>> we could provide a simple file like this and let users choose their
>> services:
>>
>> (define domain "mydomain.org")
>> ; and other common configuration options
>> …
>> (operating-system
>>   …
>>   (services
>>    (cons*
>>     ;; Uncomment for email
>>     ;(dovecot-service …)
>>     …
>>     ;; Uncomment for cgit
>>     ; (cgit-service …)
>>     …
>>     )))
>>
>> And then, you have a base with sane defaults for a defined purpose,
>but
>> can still tweak and change things.
>
>I like this.
>
>The users could also be included on this configuration. I am not sure
>if
>users on the system are used also as users of the different services.
>
>It would be nice to have something that would avoid configuration file
>errors. Maybe some test that would review syntax on Emacs.
>
>Maybe the best would be that each service would be run by a different
>user
>in order to make the system more secure.
>
>Just ideas.
>Q

It's already the case in guix: for instance, we have a mariadb that runs under the mariadb user. The service definition itself extends the list of system users, so as a user it's completely transparent and you can't make a mistake.

Since most services use a scheme wrapper to define their configuration, it's easy to check parameters to ensure the configuration will work. It's not done in every service, and not complete, but it's doable, not only for this project, but for any guix user. You should really go check the manual on services :)

  reply	other threads:[~2019-08-07  7:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19  4:42 personal communications server Quiliro Ordóñez
2019-08-05 19:28 ` Quiliro Ordóñez
2019-08-05 21:13   ` Ricardo Wurmus
2019-08-06  1:21     ` quiliro
2019-08-06  6:45       ` Julien Lepiller
2019-08-06 14:25         ` quiliro
2019-08-06 14:56           ` Julien Lepiller
2019-08-06 18:19             ` Ricardo Wurmus
2019-08-06 21:51               ` quiliro
2019-08-07  9:40                 ` L p R n d n
2019-08-06 21:52               ` L p R n d n
2019-08-06 21:48             ` quiliro
2019-08-07  7:00               ` Julien Lepiller [this message]
2019-08-06  8:51       ` Alex Sassmannshausen

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

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

  git send-email \
    --in-reply-to=B61F8332-FCB8-48CC-AE13-5CCA9F94B820@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=help-guix@gnu.org \
    --cc=quiliro@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.