Files
archie/deployments/docker-nats-stack.toml
T
sam 37cfe87508 fix(webui): validate mutation Origin against the effective external scheme
Origin validation compared the request's Origin against the daemon's own
direct connection: scheme from r.TLS, host from r.Host. Behind a TLS-
terminating reverse proxy the browser sends Origin: https://host while the
daemon sees a plain HTTP connection, so every dashboard mutation was
refused as cross-origin.

Taking X-Forwarded-Proto/-Host unconditionally would be worse than the bug:
any client can set them, so an exposed daemon would let an attacker forge
the scheme half of the CSRF check. They are honoured only when
web.trust_forwarded_headers is explicitly enabled, which is off by default
and documented as safe only behind a proxy that overwrites or strips
untrusted forwarded headers.

authorizeTaskMutation becomes a method because the decision now depends on
server configuration; its three call sites move with it.
2026-08-25 02:06:02 +10:00

104 lines
2.9 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"
diff_cap_lines = 0
work_dir = "~/.local/share/archie/work"
db_path = "~/.local/share/archie/archie.db"
[forge]
type = "gitea"
host = "https://git.example.com"
[forge.token]
engine = "env"
key = "ARCHIE_GITEA_TOKEN"
[dispatch]
trigger = "assignee"
ack_reaction = "eyes"
[dispatch.labels]
queued = "agent:queued"
working = "agent:working"
waiting = "agent:waiting"
pr = "agent:pr"
parked = "agent:parked"
# 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"
image = "git.example.com/you/archie-agent:latest"
max_concurrency = 4
max_uptime = "60m"
# "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]
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_env = "TELEGRAM_BOT_TOKEN"
# Empty list denies everyone.
allowed_user_ids = []