42582cb922
Some checks failed
deploy / deploy (push) Failing after 5m45s
Run 6 started every unit cleanly and still failed, at the health probe. The journal says why: "tireless-api listening", addr: "127.0.0.1:23296" while the config it had just loaded says `bind = "0.0.0.0:23296"`. The `--bind` flag carried `default_value_t`, so it was always Some, so it always won — the config field I added was never read by anything. The failure mode is the interesting part: from bob the service looks perfect. It starts, logs "listening", and answers a local curl. Only a request from the proxy that actually fronts it fails, which is why the probe was moved off loopback in the first place. Make --bind an Option with no default and fall back to config.api.bind, and add a test asserting the shipped template does not bind loopback — with the reason, so that if ingress ever moves onto bob the test explains that the bind, the firewalld service and the vhost move together. Verified end to end on the real hosts: the API binds 0.0.0.0, the proxy reaches /v1/ready across the mesh, https://tireless.internal serves both the dashboard and the API, and the served certificate matches the one on disk by serial. Refs #9 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013TxK1CWPkFXqdcXMJ4hVe6