Phase E: provision VITE_SPIRE_SEED for bunker pairing (#52) #63
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "phase-e-provisioning"
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?
Phase E of the bunker migration (#52) — the deploy/provisioning slice. Now that C (#60) and D (#61) are on
dev, this is the single remaining commit (rebased ontodev, just8a02d72).Validated on real hardware — this is the exact provisioning path used to pair the Sintra in the 2026-06-21 bunker smoke (
~/dev/coordination/smoke-bunker-pairing-sintra.md; legs 1/2/5/7/8/9 all passed).Changes
provision-atm.sh— writesVITE_SPIRE_SEED(thespire-seed:v1:pairing seed from spirekeeper) as the production identity, validating the scheme prefix; the generated nsec path is kept only as a dev fallback whenSPIRE_SEEDis unset. Relay default moved to the LNbits bundled nostrrelay (ws://$HOST_IP:5001/nostrrelay/test)..envtemplates (live.nix+ the flake's installed-default) — swapVITE_ATM_PRIVATE_KEY→VITE_SPIRE_SEED, drop the dead LP-era vars.state.dbnow also holds the bunker binding (keep it or re-pair).Note
The smoke surfaced that the Sintra's
nixos-upgrade.timerreverts anixos-rebuild testdeploy at 04:00 (channel/dev build) — a deploy-methodology gotcha, not a code issue. Not addressed here; flagged for test-unit ops.Do NOT use the MCP merge endpoint — merge via the Forgejo UI after review.
🤖 Generated with Claude Code