fix(dev): give dev:gateway the dev overlay so it reaches the dev state store
dev:daemon, dev:dashboard and dev:state-store all pass `-config-overlay deployments/dev.toml`, which is what sets [services.state].target = 127.0.0.1:9090. dev:gateway did not, so under `task dev` the gateway dialled whatever the developer's installed ~/.config/archie/config.toml named, or failed to start in a fresh checkout, while the other three processes used the dev store the task summary itself describes. No automated test accompanies this: asserting it would mean reading Taskfile.yml's text, which is the source-coupling class the tracker already files as test-coupling-6/-7. The change is a config value, verified by inspection of the four dev processes.
This commit is contained in:
1 parent
d0395cebd5
commit
fe48ffdd97
1 file changed
+6
-1
+6
-1
@@ -132,8 +132,13 @@ tasks:
|
||||
|
||||
dev:gateway:
|
||||
desc: archie-gateway only, no live-reload (prefer `task dev`)
|
||||
# The overlay carries [services.state].target, which archie-gateway
|
||||
# requires (openStateStoreAdapter fails closed on an empty target).
|
||||
# Without it `task dev` leaves the gateway dialling whatever the
|
||||
# developer's installed config names, or unable to start at all, while
|
||||
# archied, archie-ui and the state store all dial 127.0.0.1:9090.
|
||||
cmds:
|
||||
- go run ./cmd/archie-gateway
|
||||
- go run ./cmd/archie-gateway -config-overlay deployments/dev.toml
|
||||
|
||||
dev:ui:
|
||||
desc: Vite dev server only, expects archie-ui already running (prefer `task dev`)
|
||||
|
||||
Reference in new issue
Block a user