mirror of
https://blitiri.com.ar/repos/chasquid
synced 2025-12-23 15:37:01 +00:00
b1a29d8194
chasquid needs at least one certificate in order to start, to prevent accidental misconfigurations. This patch documents this in etc/chasquid/README, and while at it fixes a minor terminology issue. Thanks to Martin Ferrari for the bug report!
31 lines
914 B
Plaintext
31 lines
914 B
Plaintext
|
|
This directory contains chasquid's configuration.
|
|
|
|
- chasquid.conf Main config file.
|
|
|
|
- domains/ Domains' data.
|
|
- example.com/
|
|
- users User and password database for the domain.
|
|
- aliases Aliases for the domain.
|
|
...
|
|
|
|
- certs/ Certificates to use, one dir per pair.
|
|
- example.com/
|
|
- fullchain.pem Certificate (full chain).
|
|
- privkey.pem Private key.
|
|
...
|
|
|
|
|
|
Note the certs/ directory matches certbot's structure, so if you use it you
|
|
can just symlink to /etc/letsencrypt/live.
|
|
|
|
You need at least one certificate, or the server will refuse to start.
|
|
Ideally there should be a certificate for each DNS name pointing to you.
|
|
|
|
Make sure the user you use to run chasquid under ("mail" in the example
|
|
systemd files) can access the certificates and private keys.
|
|
|
|
|
|
The user databases can be created and edited with the chasquid-util tool.
|
|
|