fd4614a7d07fa9f27542df619919b371d8bf52a8
install.sh produces config.toml two ways, and neither emitted an active [services.state].target. The self-host branch writes a hand-rolled heredoc with no [services] section at all, and the non-self-host branch rewrites only the [forge] block of config.example.toml -- where [services.state] sat commented out. openStateStoreAdapter requires a target, so a freshly installed archied aborted at startup with no way to boot from the config the installer had just written. Activate [services.state] with a loopback target in both sources, which is the producer fix: the config the installer emits is the invalid state, so it is corrected where it is generated rather than defended against at the daemon. [services.gateway] is activated alongside it for the same reason it is safe to -- internal/infrastructure/configuration/defaults.go already defaults that target to 127.0.0.1:8585, so declaring it changes no resolved value and only makes the emitted config explicit. Add TestInstallerGeneratedConfigHasServiceTargets, which parses what each branch actually produces: config.example.toml through the real config loader, and the install.sh heredoc reconstructed with its shell expansions resolved. Both assertions are red-first -- with the sources reverted the test fails on both branches with the boot-fatal message. Found by an adversarial package sweep (temp tracker: repo-root-deployment-1, .local/issue-tracker/).
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.8%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%