mirror of
https://blitiri.com.ar/repos/chasquid
synced 2026-10-29 15:02:30 +00:00
Alberto Bertogli
e417d67f7c
In commit 3f9d0c0762, we added a new possible private file. If the file exists but there's an error reading it (common for permission issues), currently we just move on to the next file, and if it doesn't exist we may give up with that error. That can "hide" the access problems making them harder to debug. To help with those kinds of errors, this patch updates the logic to return an error if a private key exists but is inaccessible. It also adds an unit test for this function to cover the different scenarios, and updates the docs to match.
32 lines
1008 B
Plaintext
32 lines
1008 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 (can also be named key.pem).
|
|
...
|
|
|
|
|
|
Note the certs/ directory matches certbot's structure, so if you use it you
|
|
can just symlink to /etc/letsencrypt/live.
|
|
The NixOS ACME module's layout (/var/lib/acme) is also supported.
|
|
|
|
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.
|
|
|