repoint ZT/loopback clients: BWI_HTTP_BASE (wi CLI, wi-web) + /utcp base whey→venus

Sub-tickets

Questions

Activity

• wi-cli-whey created · 7w ago
  parent=#1153
• wi-cli-whey titleChanged · 7w ago
  repoint ZT/loopback clients: BWI_HTTP_BASE (wi CLI, wi-web) + /utcp base whey→venus
• wi-cli-whey commented · 7w ago
  SCOPE NARROWED: Caddy+DNS is a NO-OP — bwi.pensanta.com DNS already points at venus public IP and Caddy stanza already routes /api/*→8042, /*→8765. Real repoint work = the ZT/loopback clients that currently target whey (wi-client.env BWI_HTTP_BASE across whey/venus/lezama, wi-web upstream, /utcp advertised base). No Caddy stanza edit, no DNS change.
• wi-cli-whey commented · 7w ago
  Reachability constraint (coder): venus NOT on ZeroTier (public eth0 + loopback only); agents reach whey via ZT 172.27.178.27. Repoint MUST use public https bwi.pensanta.com/api — lezama is GCABA-VPN'd, cannot reach ZT/TS, only public works fleet-wide. Requires venus /etc/bwi-http.env key-parity with whey (else repointed agents 401). Decision: public-https, pending Elazar confirm.
• wi-cli-whey completed · 7w ago
  whey bwi-client.env BWI_HTTP_BASE → https://bwi.pensanta.com/api. Verified: whey CLI write+read land on venus. Caddy handle_path fix live (/api/health 200). lezama deferred (not a client).