disinto/projects/disinto.toml.example
Claude 78a295f567
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
ci/woodpecker/push/nomad-validate Pipeline was successful
ci/woodpecker/pr/ci Pipeline was successful
ci/woodpecker/pr/edge-subpath Pipeline was successful
ci/woodpecker/pr/nomad-validate Pipeline was successful
ci/woodpecker/pr/smoke-init Pipeline was successful
fix: vision(#623): automate subdomain fallback pivot if subpath routing fails (#1028)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-20 11:12:20 +00:00

81 lines
2.9 KiB
Text

# projects/disinto.toml.example — Template for disinto self-management
#
# Copy to projects/disinto.toml and fill in box-specific values,
# or run: disinto init johba/disinto
name = "disinto"
repo = "johba/disinto"
ops_repo = "disinto-admin/disinto-ops"
forge_url = "http://localhost:3000"
repo_root = "/home/YOU/dark-factory"
ops_repo_root = "/home/YOU/disinto-ops"
primary_branch = "main"
[ci]
woodpecker_repo_id = 0
stale_minutes = 60
[services]
containers = []
[monitoring]
check_prs = true
check_dev_agent = true
check_pipeline_stall = false
# Agent scheduling configuration
#
# These values are passed to the agents container as environment variables.
# The default values (6 hours each) work well for stable production projects.
# For active development on the disinto factory itself, you may want to
# configure shorter intervals:
#
# GARDENER_INTERVAL=3600 # 1 hour (default: 21600 = 6 hours)
# ARCHITECT_INTERVAL=540 # 9 minutes (default: 21600 = 6 hours)
# PLANNER_INTERVAL=660 # 11 minutes (default: 43200 = 12 hours)
#
# These can be set in docker-compose.yml environment section or in a .env file.
#
# [agents.schedule]
# gardener_interval = 21600 # seconds (default: 21600 = 6 hours)
# architect_interval = 21600 # seconds (default: 21600 = 6 hours)
# planner_interval = 43200 # seconds (default: 43200 = 12 hours)
# Local-model agents (optional) — configure to use llama-server or similar
# for local LLM inference. Each agent gets its own container with isolated
# credentials and configuration.
#
# When enabled, `disinto init` automatically:
# 1. Creates a Forgejo bot user matching agents.llama.forge_user
# 2. Generates FORGE_TOKEN_<BOT> and FORGE_PASS_<BOT> (stored in .env.enc)
# 3. Adds the bot user as a write collaborator on the project repo
#
# [agents.llama]
# base_url = "http://10.10.10.1:8081"
# model = "unsloth/Qwen3.5-35B-A3B"
# api_key = "sk-no-key-required"
# roles = ["dev"]
# forge_user = "dev-qwen"
# compact_pct = 60
# poll_interval = 60
# Edge routing mode (default: subpath)
#
# Controls how services are exposed through the edge proxy.
# subpath — all services under <project>.disinto.ai/{forge,ci,chat,staging}
# subdomain — per-service subdomains: forge.<project>, ci.<project>, chat.<project>
#
# Set to "subdomain" if subpath routing causes unfixable issues (redirect loops,
# OAuth callback mismatches, cookie collisions). See docs/edge-routing-fallback.md.
#
# Set in .env (not TOML) since it's consumed by docker-compose and shell scripts:
# EDGE_ROUTING_MODE=subdomain
#
# In subdomain mode, `disinto edge register` also writes:
# EDGE_TUNNEL_FQDN_FORGE=forge.<project>.disinto.ai
# EDGE_TUNNEL_FQDN_CI=ci.<project>.disinto.ai
# EDGE_TUNNEL_FQDN_CHAT=chat.<project>.disinto.ai
# [mirrors]
# github = "git@github.com:johba/disinto.git"
# codeberg = "git@codeberg.org:johba/disinto.git"