The chat agent's file tools operate on host paths, so the daemon has to see the host filesystem. It keeps spawning agent containers through the Docker socket and talking to NATS, so compose still carries the bus and the network; archied and watchtower leave it. Pins the network subnet: the daemon hands agent containers its own nats.url verbatim, so that URL has to work from the host and from inside a container. The gateway address does; a Docker-assigned subnet would move it silently when the network is recreated.
Archie Core Deployment Examples
This directory contains configuration templates and guides for different deployment scenarios of Archie Core.
Directory Structure
-
single-forge-github.toml: Standard single-forge deployment managing multiple GitHub repositories under a single bot account and GitHub token. -
multi-forge-github-gitea.toml: Multi-identity deployment running GitHub and a self-hosted Gitea instance simultaneously with distinct bot accounts, tokens, and repository sets. -
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: The repository'sdocker-compose.ymlstack —archiedorchestrating sandboxedarchie-agentcontainers 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: Operational runbook for runningarchiedas a persistent 24/7 background service via systemd user units andloginctl enable-linger.
Usage
Copy any scenario template to your XDG configuration directory (${XDG_CONFIG_HOME:-~/.config}/archie/config.toml):
mkdir -p ~/.config/archie
cp deployments/single-forge-github.toml ~/.config/archie/config.toml
Edit API keys in ~/.config/archie/env or directly in config.toml, then launch Archie Core:
archied
# or via systemd:
systemctl --user start archied