Files
archie/deployments/standalone.toml
T
sam 0346bfef77 fix(configuration): require containers.image instead of a private-registry default (#2054)
applyContainerDefaults no longer fills containers.image with a hard-coded
private-registry reference. An unset image now fails configuration
validation with 'containers.image is required for autonomous workflow
workers', so a fresh instance is told at startup (and via the readiness
probe at runtime) instead of at the first failed container pull.

Configs that relied on the default now set it explicitly: dev.toml (the
local task image:agent build, which e2e also overlays), plus commented
[containers] blocks in config.example.toml and standalone.toml. The
deploy docs no longer describe a code-level default.
2026-11-21 01:16:41 +11:00

69 lines
2.6 KiB
TOML

# ==============================================================================
# Minimal event-driven deployment: no forge, no repositories
#
# Events arrive as webhooks at the dashboard and run workflows. Models run
# locally through Ollama; for a hosted provider replace [providers.ollama] with
# e.g. [providers.openai] class = "openai", api_key_env = "OPENAI_API_KEY"
# and change the model names to "openai/<model>".
# ==============================================================================
# Standalone still needs a bot identity: it names the agent that chat turns and
# the session curator attribute memory to, and it becomes the seeded identity's
# display name when there is no [[identities]] block.
bot_user = "archie"
work_dir = "~/.local/share/archie/work"
state_dir = "~/.local/share/archie" # NATS store, task logs
# PostgreSQL 18 connection (required).
# `docker compose up -d postgres` provides the local default; point it at
# your own Postgres 18 server otherwise. The services serve as archie_runtime
# and migrations run as archie_migrator; create both once with
# `archie-state-store provision -h` (deployments/README.md).
database_url = "postgres://archie_runtime:archie@127.0.0.1:5432/archie?sslmode=disable"
migration_database_url = "postgres://archie_migrator:archie@127.0.0.1:5432/archie?sslmode=disable"
[services.gateway]
target = "127.0.0.1:8585"
# The State Store gRPC service owns the PostgreSQL task data; archied and
# archie-gateway dial it and never open those tables themselves.
# Host-only deployment: the agent runs on the host, so the loopback target
# 127.0.0.1:9090 needs no token. Start archie-state-store with the matching
# `-listen 127.0.0.1:9090`.
[services.state]
target = "127.0.0.1:9090"
# Standalone execution: Forge polling is disabled
[forge]
type = "none"
[models]
triage = "ollama/llama3:latest"
planner = "ollama/llama3:latest"
builder = "ollama/llama3:latest"
[providers.ollama]
class = "ollama"
# Optional chat workspace configuration
[chat]
operator = "Local Operator"
workspace = "~/.local/share/archie/workspace"
max_steps = 100
models = [
"ollama/llama3:latest",
"ollama/qwen2.5:7b"
]
[budgets]
max_steps = 60
wall_clock = "30m"
# The image task containers run. There is no default: the daemon refuses to
# start without it and names the key, so set your own pinned reference here --
# see deployments/systemd-user-service.md#6-pinning-the-archie-agent-image.
# [containers]
# image = "registry.example.com/archie/archie-agent@sha256:<digest>"
# pull_policy = "missing"
# registry_auth = { engine = "env", key = "ARCHIE_REGISTRY_AUTH" } # when the registry needs a login