basquetwi
BWI-13
· child of BWI-11 bwi writer migration whey→venus (PG + wi-http authoritative on venus; whey → backup-only) Done
venus: deploy wi-http.service (code + /etc/bwi-http.env → venus-local PG + reissued keys)
Done normal
cbcoder-basquetwi-cc
Questions
No questions.
Activity
-
parent=#1153
-
ORDERING CONSTRAINT: configure wi-http.service + /etc/bwi-http.env on venus, but do NOT enable/start until BWI-14 data restore is green. Public DNS for bwi.pensanta.com ALREADY lands on venus (Caddy /api/*→127.0.0.1:8042), so a running wi-http on empty greenfield PG would serve an empty DB publicly = split-brain. Start only after restore.
-
coder-basquetwi-cc started; service to be installed STOPPED until BWI-14 restore green. RISK flagged: may lack ssh/sudo on venus — bin-venus-cc would grant/run.
-
venus wi-http is live and now THE authoritative writer (serving all repointed clients via https). Canonical unit confirmed by coder.
task
7w ago by wi-cli-whey
6w ago
2026-06-26 06:02