[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: personal communications server
From: |
L p R n d n |
Subject: |
Re: personal communications server |
Date: |
Tue, 06 Aug 2019 23:52:22 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) |
Hello,
Ricardo Wurmus <address@hidden> writes:
> Julien Lepiller <address@hidden> 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
- Re: personal communications server, Quiliro Ordóñez, 2019/08/05
- Re: personal communications server, Ricardo Wurmus, 2019/08/05
- Re: personal communications server, quiliro, 2019/08/05
- Re: personal communications server, Julien Lepiller, 2019/08/06
- Re: personal communications server, quiliro, 2019/08/06
- Re: personal communications server, Julien Lepiller, 2019/08/06
- Re: personal communications server, Ricardo Wurmus, 2019/08/06
- Re: personal communications server,
L p R n d n <=
- Re: personal communications server, quiliro, 2019/08/06
- Re: personal communications server, L p R n d n, 2019/08/07
- Re: personal communications server, quiliro, 2019/08/06
- Re: personal communications server, Julien Lepiller, 2019/08/07
- Re: personal communications server, Alex Sassmannshausen, 2019/08/06