NEC-352: install-deployer.sh --check reports a month-stale deployer as verified #324
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!324
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-352-install-deployersh-check-reports-a-month"
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-352 — https://projectron.nerchure.com/tasks/373
install-deployer.sh --check and inventory.mjs compared only docker-compose.yml and the Caddyfile, so on 27 Oct both called eu1 and accounts verified while they ran the 26 September deployer. deploy/host-files.txt is now the one list of every file a host carries (deployer, units, backup script, Kuma bundle, compose, Caddyfile, deploy.env.example; snapshot.sh on ops). The installer copies exactly its rows (to .new, moved in once every copy lands; a failed copy is taken back), --check and the inventory compare exactly its rows with the identity host's units rewritten as installed, and the console's installer copies every source it names. Both installers build the Kuma bundle via lib/bundle-kuma.sh, so the console's copy matches the hosts'. A file the checker cannot read is reported absent-here, not dropped. A Caddyfile Caddy will not load now fails the install on the ops box too. New deploy/test/install-deployer.test.ts runs the real installer against a fake host; every new rule mutation-checked. Decision recorded: no self-reported deployer hash; automatic staleness signal filed as NEC-355. After merge, run deploy/install-deployer.sh once: every shard and identity host will show deployer and bundle drift until it runs.
Spec:
docs/changes/NEC-352-install-deployer-check/spec.mdChangelog
NONE
07512a71302c047771ac