chore(deploy): commit the compose stack, drop the required overlay

docker-compose.yml was never committed -- it only existed on the
deployment host. It bind-mounted ./config.docker.toml and passed
-config-overlay unconditionally, which made an untracked repo-root
file load-bearing: Docker creates a directory when a bind source is
missing, and the loader rejects a directory, so a fresh clone took the
daemon down at boot.

The stack now passes a single -config pointing at a path outside the
repo. Nothing in the working tree is required at runtime. The
docker-specific values move to deployments/docker-nats-stack.toml as a
reference config, alongside the other deployment guides.

Also drops the ./:/workspace mount, which existed only for
desktop-commander's work_dir.
This commit is contained in:
sam committed 2026-07-31 01:13:23 +10:00
1 parent bc5d8dcdc9
commit 3ee3bcf202
3 files changed
+188

No files matched your search

+3
View File
@@ -13,6 +13,9 @@ This directory contains configuration templates and guides for different deploym
* **[`local-ollama-standalone.toml`](./local-ollama-standalone.toml)**:
Self-hosted deployment running local LLM models via Ollama (e.g., `llama3`, `qwen2.5`) with optional standalone (forge-disabled) operation.
* **[`docker-nats-stack.toml`](./docker-nats-stack.toml)**:
The repository's `docker-compose.yml` stack — `archied` orchestrating sandboxed `archie-agent` containers over NATS. Copy to `~/.config/archie/config.toml`; the compose file mounts that path and passes it as the only `-config`.
* **[`systemd-user-service.md`](./systemd-user-service.md)**:
Operational runbook for running `archied` as a persistent 24/7 background service via systemd user units and `loginctl enable-linger`.
+104
View File
@@ -0,0 +1,104 @@
# Docker Compose + NATS deployment.
#
# Copy to ~/.config/archie/config.toml -- docker-compose.yml mounts that path
# read-only at /etc/archie/config.toml. This is a complete config, not an
# overlay: the stack passes a single -config flag, so nothing in the repo
# working tree needs to exist for the daemon to boot.
#
# mkdir -p ~/.config/archie
# cp deployments/docker-nats-stack.toml ~/.config/archie/config.toml
# docker compose up -d
#
# Paths below are container paths. docker-compose.yml maps them to host
# volumes (/var/lib/archie/work and /var/lib/archie/db).
poll_interval = "60s"
bot_user = "archie"
diff_cap_lines = 0
work_dir = "/var/lib/archie/work"
db_path = "/var/lib/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 daemon image. Setting
# containers.enabled selects nats mode on its own, but pinning it here keeps
# the intent explicit.
[agent]
mode = "nats"
[nats]
# "nats" is the compose service name, resolved on the stack's own network.
url = "nats://nats:4222"
[containers]
enabled = true
network = "archie-core_default"
image = "git.example.com/you/archie-agent:latest"
max_concurrency = 4
max_uptime = "60m"
pull_policy = "if-not-present"
[web]
# 0.0.0.0 so the dashboard is reachable through the published port.
listen = "0.0.0.0:8484"
[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
max_tokens = 100000000
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 appear BOTH in the host .env and in
# docker-compose.yml's `environment:` passthrough list -- a missing
# passthrough silently yields an empty value.
[chat.telegram]
token_env = "TELEGRAM_BOT_TOKEN"
# Empty list denies everyone.
allowed_user_ids = []
+81
View File
@@ -0,0 +1,81 @@
# archie-core stack: daemon, NATS, and agent containers.
#
# Start: docker compose up -d
# Stop: docker compose down
# Logs: docker compose logs -f archied
services:
# ── NATS JetStream ────────────────────────────────────────────────
nats:
image: nats:2.14-alpine3.22
command: -js -m 8222
ports:
- "4222:4222" # client
- "8222:8222" # monitoring (http://localhost:8222)
volumes:
- nats_data:/data
restart: unless-stopped
healthcheck:
test: ["CMD", "wget", "-q", "-O", "-", "http://localhost:8222/healthz"]
interval: 10s
timeout: 5s
retries: 5
# ── archie daemon ──────────────────────────────────────────────────
archied:
image: git.catlow.cloud/sam/archied:latest
# Single config, mounted from outside the repo. Nothing in the working
# tree is required at runtime: a bind mount whose source is missing is
# created as a directory, and the loader rejects a directory, so a
# repo-root config file would take the daemon down on a fresh clone.
# See deployments/docker-nats-stack.toml for the template.
command: -config /etc/archie/config.toml
extra_hosts:
- "host.docker.internal:host-gateway"
ports:
- "8484:8484" # web dashboard
environment:
- ARCHIE_GITEA_TOKEN
- ARCHIE_GITEA_TOKEN_ARCHIE
- HEYARCHIE_TELEGRAM_BOT_TOKEN
- DEEPSEEK_API_KEY
volumes:
- ${HOME}/.config/archie/config.toml:/etc/archie/config.toml:ro
- /var/lib/archie/work:/var/lib/archie/work
- /var/lib/archie/db:/var/lib/archie
- /var/run/docker.sock:/var/run/docker.sock
depends_on:
nats:
condition: service_healthy
restart: unless-stopped
# ── agent image (built once, spawned per task by the daemon) ───────
# Not a long-running service: the daemon starts agent containers itself
# via the Docker socket. This stanza exists so `docker compose build`
# produces the image locally.
agent:
build:
context: .
dockerfile: Dockerfile
image: git.catlow.cloud/sam/archie-agent:latest
command: ["true"]
entrypoint: [""]
restart: "no"
# ── deploy watcher ──────────────────────────────────────────────────
# Polls the registry for new archied/archie-agent images (pushed by
# .gitea/workflows/deploy.yml on merge to main) and restarts the
# containers that changed. Registry auth comes from the host's
# existing `docker login` config, mounted read-only.
watchtower:
image: nickfedor/watchtower
environment:
- DOCKER_CONFIG=/
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- ${HOME}/.docker/config.json:/config.json:ro
command: --interval 60 --cleanup archie-core-archied-1
restart: unless-stopped
volumes:
nats_data: