ghcr.io/samcharles93/archie-agent:latest is re-published on every main push that touches the runtime's package closure, so a bare :latest reference can change under a running deployment with no warning and no way to reproduce a prior build. archie-agent has no published semver tag yet -- CI (deploy.yml) only ever pushes :latest to GHCR, confirmed via the GHCR package API. Pin docker-compose.yml and the GitHub deployment profiles to the verified digest of :latest as of 2026-09-05 (sha256:870f1b1357979cfea23fccacb24166ebeb9ab321708ef2c2b218a763ed99b090), and document the pinning strategy -- including the semver-tag-once- published preference and digest pinning for production -- in deployments/systemd-user-service.md. Update the generic docker-nats-stack.toml example to demonstrate the same convention. Ref archie-core-kllw (GitHub #670)
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: Host-runarchiedorchestrating sandboxedarchie-agentcontainers over the repository's Compose-managed NATS service. Copy to~/.config/archie/config.toml, start NATS with Compose, then startarchiedon the host. -
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