No description
affbb703be
Caddy glob-imports Caddyfile.d/ once, at startup, and its own unit does not change when a fragment does — so NixOS left it running and the vhost simply did not exist. No listener, no certificate, and nothing in the log to say why, because Caddy had never been told to look. The first deploy of this module hit exactly that: it had to be reloaded by hand before ACME would even try. reloadTriggers makes the fragment's content part of what decides whether Caddy is reloaded, so this cannot recur the next time the domain or the port moves. Also answer unmatched paths with 404. Caddy's default for a request that matched no route is an empty 200, which made every stray path — /config.yml among them — look like an empty file that exists. Nothing was ever served either way, but 404 is the honest answer. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| bin | ||
| .gitignore | ||
| apps.nix | ||
| fdroid-sync.py | ||
| flake.lock | ||
| flake.nix | ||
| module.nix | ||
| README.md | ||