From: quiliro@riseup.net
To: help-guix <help-guix@gnu.org>
Subject: Re: personal communications server
Date: Tue, 6 Aug 2019 16:48:29 -0500 [thread overview]
Message-ID: <6c155c97ee82a33f962788b887cda397.squirrel@sm.riseup.net> (raw)
In-Reply-To: <BC59910C-0CE5-4E79-A720-A548169378B8@lepiller.eu>
> 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
next prev parent reply other threads:[~2019-08-06 21:48 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 [this message]
2019-08-07 7:00 ` Julien Lepiller
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
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=6c155c97ee82a33f962788b887cda397.squirrel@sm.riseup.net \
--to=quiliro@riseup.net \
--cc=help-guix@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.
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).