# Development overlay for `task dev` and `task dev:dashboard`. # # Match Vite's API/event proxy without changing the installed configuration. # The dashboard on :8484 is the # archie-ui process's listener, not archied's; this overlay is what both # `go run ./cmd/archied -config-overlay deployments/dev.toml` and # `go run ./cmd/archie-ui -config-overlay deployments/dev.toml` read. Only # [web], [services.*] and [capture] land in archie-ui; the daemon ignores # [web] entirely. # `task dev` runs archie-state-store against this overlay, and the State Store # fails closed without a PostgreSQL URL. This must reach the `postgres` # service in docker-compose.yml, which `task dev` brings up first via # dev:postgres -- keep the URL and that service in agreement. bot_user = "archie-dev" database_url = "postgres://archie:archie@127.0.0.1:5432/archie?sslmode=disable" [web] listen = "127.0.0.1:8484" # `task dev` runs archie-state-store via dev:state-store, which passes no # -listen, so the listen below is the port the store binds. It must agree with # the target: these two lines are the only place that pair is stated. Move them # when a port is already taken on the host -- before the # listen key existed the collision could only be worked around by hand-writing # a matching target and passing -listen, and it read as a code fault. # # Task containers dial the target over the Docker bridge gateway, so the store # listens on every interface and [tls] (issued by `task dev:tls`) is required. [services.state] target = "172.17.0.1:9091" listen = "0.0.0.0:9091" [tls] ca_file = "tmp/dev-tls/ca.pem" cert_dir = "tmp/dev-tls" # `task dev` runs archie-gateway via dev:gateway, which also passes no -listen: # the listen below is what it binds. Stated explicitly so the value archie-ui # dials is visible next to the State Store one. [services.gateway] target = "127.0.0.1:8585" listen = "127.0.0.1:8585" [services.daemon] target = "127.0.0.1:8587" listen = "127.0.0.1:8587"