Files
archie/deployments/docker-nats-stack.toml
T
sam c54d328f0d feat(store): run services as a non-superuser role and name every connection (#1857)
Every service connected to PostgreSQL as the database owner, which is a
superuser, so anything that compromised an app process owned the cluster, and
every connection reached the server with an empty application_name, so
pg_stat_activity could not say which service a session belonged to.

Split the DB credential into two login roles and name every pool:

- archie_migrator owns public and its objects and runs goose. Migrations run
  on a short-lived pool opened from the new migration_database_url, before the
  serving pool opens. It is not a superuser.
- archie_runtime serves requests with SELECT, INSERT, UPDATE, DELETE, sequence
  USAGE/SELECT and function EXECUTE only. It has no CREATE privilege, so it
  cannot change the schema.
- Every pool sets application_name: archie-state-store, archie-gateway, and a
  -migrate / -recovery / -schema / -provision suffix on the transient
  administrative connections. Existing one-URL installs keep working: an
  absent migration_database_url falls back to database_url and the migration
  runs on the serving pool exactly as before.

Provisioning is a new idempotent `archie-state-store provision` subcommand: it
needs an admin URL the services never hold (database owner or superuser),
creates or reconciles both roles, hands every public-schema object to the
migration role, revokes PUBLIC's CREATE on public, sets row-level grants, and
sets the migration role's default privileges so tables future migrations
create are usable without a hand-run grant. It stores SCRAM verifiers, refuses
superuser roles, and verifies the boundary before committing.

install.sh now provisions the bundled path and separates the credentials: the
superuser password the Compose database is created with lives only in a
compose-only postgres.env, while the env file the units load holds the
non-superuser PGPASSWORD. A bundled install that predates the split is
upgraded in place: the roles are created, the superuser password is rotated
out of the env file, and config.toml is moved to the runtime and migration
URLs. External databases keep their operator-managed credential; the
deployments README documents the one-shot provision command.

setup writes both bundled URLs, dev:postgres provisions the dev database, the
e2e stack provisions its throwaway server, and the deployment templates point
at the two roles.
2026-11-11 03:12:54 +11:00

126 lines
4.4 KiB
TOML

# Host daemon + Docker Compose NATS deployment.
#
# Copy to ~/.config/archie/config.toml. docker-compose.yml starts NATS only;
# run archied on the host (for example with systemd-user-service.md). This is
# a complete config, not an overlay.
#
# mkdir -p ~/.config/archie
# cp deployments/docker-nats-stack.toml ~/.config/archie/config.toml
# docker compose up -d nats
# archied -config ~/.config/archie/config.toml
#
# Paths below are host paths. Explicit home-relative paths are expanded.
poll_interval = "60s"
bot_user = "archie"
work_dir = "~/.local/share/archie/work"
state_dir = "~/.local/share/archie" # NATS store, task logs
# The State Store's PostgreSQL connection (PostgreSQL 18, required).
# `docker compose up -d postgres` provides the local default; point it at
# your own Postgres 18 server otherwise. The services serve as archie_runtime
# and migrations run as archie_migrator; create both once with
# `archie-state-store provision -h` (deployments/README.md).
database_url = "postgres://archie_runtime:archie@127.0.0.1:5432/archie?sslmode=disable"
migration_database_url = "postgres://archie_migrator:archie@127.0.0.1:5432/archie?sslmode=disable"
[services.gateway]
target = "127.0.0.1:8585"
# The State Store gRPC service owns the PostgreSQL task data; archied and
# archie-gateway dial it and never open those tables themselves.
# This deployment runs the agent in containers, so the target is the Docker
# bridge gateway (172.17.0.1) the container can reach. A non-loopback address
# needs [tls]; see config.example.toml.
[services.state]
target = "172.17.0.1:9090"
[tls]
ca_file = "/etc/archie/tls/ca.pem"
cert_dir = "/etc/archie/tls"
[forge]
type = "gitea"
host = "https://git.example.com"
[forge.token]
engine = "env"
key = "ARCHIE_GITEA_TOKEN"
[dispatch]
trigger = "assignee"
ack_reaction = "eyes"
# Stages run in sandboxed archie-agent containers over NATS. archied only
# orchestrates: the agent image carries the toolchain and makes the model
# calls, so gate commands resolve there, not in the native daemon.
[nats]
mode = "external"
# The pinned Compose-network gateway is reachable from both the host daemon
# and the task containers it launches on archie-core_default.
url = "nats://172.19.0.1:4222"
[containers]
network = "archie-core_default"
# Pin your own registry's tag/digest -- never deploy against a bare
# ":latest" reference, which can change under a running deployment with no
# warning. See deployments/systemd-user-service.md#6-pinning-the-archie-agent-image
# for the pinning convention this repo follows for its own agent image.
image = "git.example.com/you/archie-agent:v1.21.0" # or "@sha256:..." for a production digest pin
max_concurrency = 4
# Must outlast the whole-task limit (default 4h), or the reaper ends a run the
# task budget would have parked.
max_uptime = "5h"
# "missing": pull only when the image is absent locally. "always" against a
# private registry answers 401 because the daemon sends no credentials, so
# refresh the agent by hand: docker compose pull agent
pull_policy = "missing"
[web]
# Bound by the archie-ui process; it dials the [services.*] targets above --
# the bridge-gateway State Store address works from the host too.
listen = "127.0.0.1:8484"
# Trust X-Forwarded-Proto when fronted by a reverse proxy (e.g. Traefik)
# terminating TLS so dashboard mutations succeed with external HTTPS Origin.
trust_forwarded_headers = true
[models]
triage = "deepseek/deepseek-v4-pro"
planner = "deepseek/deepseek-v4-pro"
builder = "deepseek/deepseek-v4-pro"
[providers.deepseek]
class = "deepseek"
api_key_env = "DEEPSEEK_API_KEY"
# A local model server is reached from the agent container, not the daemon,
# so localhost would be the container itself -- use host.docker.internal and
# give the agent containers an extra_hosts entry.
# [providers.local]
# class = "openai"
# base_url = "http://host.docker.internal:8081/v1"
# api_key_env = "LOCAL_API_KEY"
[budgets]
max_steps = 90
wall_clock = "60m"
gate_max_failures = 5
[[repos]]
owner = "you"
name = "your-repo"
base = "main"
ecosystem = "go"
gate = [
["go", "vet", "./..."],
["go", "build", "./..."],
["go", "test", "./...", "-count=1"],
]
# Every env var named here must be present in the environment of the host
# archied process, normally through its configured supervisor or launch shell.
[chat.telegram]
token = { engine = "env", key = "TELEGRAM_BOT_TOKEN" }
# Empty list denies everyone.
allowed_user_ids = []