The agent service created a container that exited 0 immediately while compose reported it as "Started", which reads like a crash loop. A build profile keeps it out of `up -d`; naming it still works for build and pull. containers.pull_policy was "if-not-present", which is not a recognised value -- the pool pulls only when it is "always" or "missing", so the typo disabled pulling outright and the deployed agent image drifted a day behind the daemon. Watchtower cannot cover for it: agent containers are spawned per task, and it only restarts long-running ones.
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