From: L p R n d n <guix@lprndn.info>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: quiliro@riseup.net, help-guix@gnu.org
Subject: Re: personal communications server
Date: Tue, 06 Aug 2019 23:52:22 +0200 [thread overview]
Message-ID: <87tvaurmg9.fsf@lprndn.info> (raw)
In-Reply-To: <87r25yxild.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 06 Aug 2019 20:19:10 +0200")
Hello,
Ricardo Wurmus <rekado@elephly.net> writes:
> Julien Lepiller <julien@lepiller.eu> writes:
>
>> 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.
>
> Or we could provide a procedure generating an operating system
> configuration. The procedure’s arguments would be used to enable or
> disable certain services.
Just being curious here, why a whole operating system configuration? Why
not just a list of services?
Thanks,
L p r n d n
> --
> Ricardo
next prev parent reply other threads:[~2019-08-06 19:52 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 [this message]
2019-08-06 21:48 ` quiliro
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvaurmg9.fsf@lprndn.info \
--to=guix@lprndn.info \
--cc=help-guix@gnu.org \
--cc=quiliro@riseup.net \
--cc=rekado@elephly.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.