Bead archie-core-8cda.5.5: - task dev now runs archie-ui (dev:dashboard) on :8484 -- after the cutover archied binds no dashboard listener, and Vite's /api,/events proxy needs a live receiver there. dev:mobile starts archie-ui with a LAN bind and -token-file (reusing the pre-cutover token path) instead of a mobile archied overlay; dev:ui's summary points at archie-ui. - deployments/dev.toml documents itself as the archie-ui overlay and states the [services.gateway] target explicitly. - systemd-user-service.md: the auth gap is now the documented posture -- archie-ui has no secret registry, resolves GATEWAY_TOKEN/ STATE_STORE_TOKEN from its process environment only, so the starter (EnvironmentFile) exports them; worked env-file example added, plus /healthz as the token-free liveness probe. - INSTRUCTIONS.md ships five binaries with archie-ui in the quickstart and the token story; README.md carries the auth note; the docker-nats-stack profile notes archie-ui binds [web] and dials the same [services.*] targets. - release tooling: archied's component closure extends with cmd/archie-ui and internal/app/archieui, so a UI-process-only commit can no longer fall between the two changelogs; RELEASING.md documents that the UI Service ships inside the archied release.
79 lines
3.7 KiB
Markdown
79 lines
3.7 KiB
Markdown
# Running this distribution
|
|
|
|
This archive contains five linux/amd64 binaries:
|
|
|
|
- **`archied`** — the resident daemon: polls your forge for assigned issues
|
|
and dispatches them into sandboxed `archie-agent` containers. It serves no
|
|
dashboard: the web UI is `archie-ui`'s process (UI cutover,
|
|
`archie-core-8cda.5.4`).
|
|
- **`archie-ui`** — serves the operator dashboard and the webhook capture
|
|
receiver, dialing the Gateway and State Store gRPC contracts. Reads only
|
|
`[services.*]`, `[web]` and `[capture]` from the shared `config.toml`.
|
|
- **`archie-gateway`** — serves the chat (`ChatContract`) surface `archied`
|
|
and `archie-ui` dial for Telegram/webhook chat. Runs as its own process;
|
|
`archied` never embeds a gateway.
|
|
- **`archie-state-store`** — owns the single `archie.db` SQLite file behind
|
|
a gRPC contract. `archied` and `archie-gateway` are gRPC clients of it, not
|
|
owners of the database.
|
|
- **`archie-playbooks`** — standalone CLI to lint playbook binding YAML
|
|
before it reaches `archied`.
|
|
|
|
`archie-agent` (the per-task sandboxed runtime) is **not** in this archive —
|
|
it only ever runs inside the Docker container `archied` spawns per task, never
|
|
as a host binary. Pull it from GHCR: `ghcr.io/samcharles93/archie-agent`.
|
|
|
|
## Quickstart
|
|
|
|
1. Pick a starting configuration. The full set of annotated templates lives
|
|
in this repository's `deployments/` directory on GitHub
|
|
(<https://github.com/samcharles93/archie-core/tree/main/deployments>) —
|
|
`single-forge-github.toml`, `multi-forge-github-gitea.toml`,
|
|
`local-ollama-standalone.toml`, and `docker-nats-stack.toml` cover the
|
|
common cases. Copy whichever fits to:
|
|
|
|
```bash
|
|
mkdir -p ~/.config/archie
|
|
cp <template>.toml ~/.config/archie/config.toml
|
|
```
|
|
|
|
2. Edit `config.toml` (forge token, repos, `[services.state]` target, model
|
|
providers) and place any secrets in `~/.config/archie/env` or referenced
|
|
`secret://` locations.
|
|
|
|
3. Start the four processes, in order (`archie-state-store` and
|
|
`archie-gateway` first — `archied` and `archie-ui` dial both at startup):
|
|
|
|
```bash
|
|
./archie-state-store -config ~/.config/archie/config.toml -listen 127.0.0.1:9090 &
|
|
./archie-gateway -config ~/.config/archie/config.toml -listen 127.0.0.1:8585 &
|
|
./archie-ui -config ~/.config/archie/config.toml &
|
|
./archied -config ~/.config/archie/config.toml
|
|
```
|
|
|
|
Dashboard reachability comes from `[web].listen` (default
|
|
`127.0.0.1:8484`, which needs no dashboard token). For a non-loopback
|
|
bind pass `-listen` with `-token` or `-token-file` to mint and persist
|
|
one. `archie-ui` reads `GATEWAY_TOKEN` / `STATE_STORE_TOKEN` from its
|
|
process environment only — it has no secret registry, so when those
|
|
tokens live in a secret manager, whatever starts `archie-ui` must export
|
|
them into its environment (the `[services.*].target_token` values in
|
|
`config.toml` are the other supported source).
|
|
|
|
4. For a persistent, 24/7 deployment instead of a foreground run, follow the
|
|
systemd user-unit runbook:
|
|
<https://github.com/samcharles93/archie-core/blob/main/deployments/systemd-user-service.md>.
|
|
|
|
## Verifying an install
|
|
|
|
`archie-playbooks lint -dir <playbooks-dir>` validates playbook binding YAML
|
|
against the same schema `archied` loads at startup — run it against your
|
|
playbooks directory before pointing `archied` at it.
|
|
|
|
## Version
|
|
|
|
This archive's binaries are built from the `archied` release tag in its
|
|
filename; `archie-ui`, `archie-gateway`, `archie-state-store`, and
|
|
`archie-playbooks` ship at that same version rather than being independently
|
|
tagged (see `RELEASING.md` in the source repository for why only `archied`
|
|
and `archie-agent` are independently versioned).
|