Wire the daemons with fx, providers in internal/sww (closes #414) #421

Merged
clawbot merged 1 commits from issue-414-fx-wiring into next 2026-11-19 11:58:21 +01:00
1 Commits
Author SHA1 Message Date
sneak 5a73af61b0 sww: wire the daemons with fx (closes #414)
check / check (push) Waiting to run
go.uber.org/fx builds the parts of waf and rproxy in internal/sww, one
provider per part. Each background loop is a lifecycle hook added where
its part is built. waf.Params takes every part built, and waf.New builds
none. GeoJS calls back into waf, so waf exports AddLookup and
GeoJSFailed, and clientGroup and banNetblock take the settings.

newServer, loadStateFiles, the inBackground list and serveRProxy are
gone. serve is the one hook that serves both daemons, and reports a
failure to run on a channel of its own; fx's signal handling is not
used. Once fx has stopped, run takes each daemon's last step: waf writes
the state files, and rproxy waits for its reports.

Model: opus-5-5
2026-11-19 09:59:52 +00:00