public: document that a Caddyfile change reloads caddy (verification for nix-config#926) #1963
No reviewers
Labels
No labels
backlog
bug
enhancement
in-progress
review
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ymrtech/nix-config!1963
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "kb/NCFG-926-caddyfile-reload-probe"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of card nix-config#926. This is the config-CONTENT-only deploy that proves the fix.
nix-config#926 (PR #1960) set services.caddy.enableReload = true on public, mail
and vpn, so the nixpkgs caddy module keeps the rendered Caddyfile in
reloadTriggersand addsExecReload = caddy reload --config ... --force.The switch that MAKES that move also changes the unit definition, so it still
restarts caddy once (the transition is unavoidable). The DoD's "a deploy that
changes the Caddyfile reloads rather than restarts" therefore needs a second
deploy whose ONLY change is the Caddyfile content - this one.
The added comment is real content of the config and is what the reviewer of this
behaviour needs to know. Evidence on the merge deploy:
ActiveEnterTimestampunchanged acrossthe deploy (a restart would change both);
systemctljournal showsReloading caddy.service .../Reloaded, with noStopping Caddy/Started Caddypair;it);
zero failed samples.
127a679dca2b21bf0543