joshsiv-mulga bb0ad3a39d fix: bind awsgw and predastore on 0.0.0.0 in spinifex.toml template ...

PR #144 (nats TLS) made every service listen on --bind's specific IP. For
awsgw and predastore this broke localhost-reachability that the UI proxy
(spinifexui/spinifexui.go:193-194) and AWS CLI spinifex profile rely on —
latent since #144, surfaced by siv-7's auto-detect default on dev installs
(502 from the UI).

Hardcode awsgw and predastore host fields to 0.0.0.0 so both listen
wildcard; loopback clients (UI proxy, spinifex AWS CLI profile, same-host
daemon → predastore) keep working, LAN clients still reach them via the
LAN-IP SAN on the cert. daemon.host and nats.host stay as {{.BindIP}}
because peer-advertised values must not resolve to 0.0.0.0/loopback.
predastore.host normalization at config.go:207 rewrites 0.0.0.0 → 127.0.0.1
for local-node consumers, so existing callers see a usable connect address.

2026-04-21 23:04:54 +10:00

..

lb-agent

feat: initial ELBv2 implementation (#122)

2026-04-10 10:27:20 +10:00

spinifex

fix: bind awsgw and predastore on 0.0.0.0 in spinifex.toml template

2026-04-21 23:04:54 +10:00