Dev loop: auto-resolve eco-server target (LAN mDNS first, tailnet FQDN fallback) #3

New issue

Closed

opened 2026-06-12 11:47:46 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-12 11:47:46 +00:00

Owner

The dev loop's eco-server base URLs (ECO_INFO_URL, ECO_ADMIN_BASE_URL, ECO_MAP_BASE_URL) default to the public eco.coilysiren.me:3001 and are only overridable by hand-exported env vars. Standing up the loop tonight required manually flipping all three to kai-server.local:3001 because the tailnet path from kais-macbook-pro is blackholed on the home LAN (Archer A20 hairpin fault, infrastructure#294 - recurrence logged there 2026-06-12).

Proposal: a small dev-target resolver, mirroring the ssh-config pattern infrastructure#294 landed.

A make / ward arg or tiny script that probes kai-server.local (mDNS, ~1s timeout) and falls through to the SSM-resolved tailnet FQDN (/coilysiren/kai-server/tailnet-fqdn) when off-LAN.
ward exec http picks the resolved base automatically so the agent or Kai never hand-assembles the three env vars.
Keep the tailnet FQDN out of tracked files per the opaque-ids rule - SSM-resolve at runtime only.

Until then the manual incantation is the three env vars prefixed onto ward exec http.

The dev loop's eco-server base URLs (`ECO_INFO_URL`, `ECO_ADMIN_BASE_URL`, `ECO_MAP_BASE_URL`) default to the public `eco.coilysiren.me:3001` and are only overridable by hand-exported env vars. Standing up the loop tonight required manually flipping all three to `kai-server.local:3001` because the tailnet path from kais-macbook-pro is blackholed on the home LAN (Archer A20 hairpin fault, infrastructure#294 - recurrence logged there 2026-06-12). Proposal: a small dev-target resolver, mirroring the ssh-config pattern infrastructure#294 landed. * A `make` / `ward` arg or tiny script that probes `kai-server.local` (mDNS, ~1s timeout) and falls through to the SSM-resolved tailnet FQDN (`/coilysiren/kai-server/tailnet-fqdn`) when off-LAN. * `ward exec http` picks the resolved base automatically so the agent or Kai never hand-assembles the three env vars. * Keep the tailnet FQDN out of tracked files per the opaque-ids rule - SSM-resolve at runtime only. Until then the manual incantation is the three env vars prefixed onto `ward exec http`.

coilysiren referenced this issue from a commit

2026-06-12 11:54:50 +00:00

feat: auto-resolve eco-server dev target in the http verb

coilysiren closed this issue

2026-06-12 11:54:50 +00:00

coilysiren referenced this issue

2026-06-17 07:29:50 +00:00

Mod-side rollout: push EcoJobsTracker.dll with lastSeen field to kai-server #31

coilysiren referenced this issue

2026-07-06 05:11:17 +00:00

Jobs page: highlight ACTIVE users, not online users #76

coilysiren referenced this issue from a commit