NEC-391: install-deployer.sh never applies a changed Caddyfile: mv breaks the single-file bind mount, and reload reads the old file #352
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
dependencies
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
security
usability
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!352
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-391-install-deployersh-never-applies-a-chang"
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?
Task: NEC-391 — https://projectron.nerchure.com/tasks/413
install-deployer.sh renamed every changed host file into place, so a Caddyfile — bind-mounted into Caddy by name on all three host kinds — reached the running Caddy never: the mount holds the old inode, and the in-container validate and reload ran on the old file and succeeded (accounts went live with feedback.nectenda.com missing from Caddy's copy, 10 Nov). Files a compose file mounts by name are now written in place; every other file, the deployer above all, is still renamed. Before reloading, the installer holds Caddy's own copy to the host's, and fails without reloading when they differ, naming the fix: validate the host's copy through the running Caddy, then restart Caddy under the deploy lock (a restart re-binds the mount and keeps the image; measured). --check makes the same comparison and keeps the stale-image line; it advises nothing for a host it could not read. Ride-along NEC-393: deploy/inventory.mjs --hosts and the console make the same comparison and show their own item. Also: deployer.sh status no longer prints 'No such file' for an env-drift file no deploy has written. No host is changed by merging; the spec's 'After merge' section lists the operator's steps.
Spec:
docs/changes/NEC-391-caddyfile-in-place/spec.mdAlso fixes NEC-393: inventory.mjs and the console compare only the host's Caddyfile, not the copy the running Caddy reads
Changelog
NONE
852c9f1e6ad395479628