Files
foreman/.env.example
T
steve 9cdf4b2472 feat: scaffold project with config, store, health endpoint, CI, and Dockerfile
Phase 1 of foreman: initialize the Go module, project layout, and core
infrastructure. Includes env-based configuration (FOREMAN_* namespace),
SQLite-backed durable job queue with WAL mode via modernc.org/sqlite,
stdlib HTTP server with /healthz and optional bearer-token auth middleware,
subcommand dispatch (serve + stubs), Gitea CI workflow, multi-stage
distroless Dockerfile, and comprehensive tests for all packages.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-23 17:58:36 -04:00

27 lines
809 B
Bash

# foreman configuration — all env vars are FOREMAN_* namespaced.
# Copy to .env and fill in values for local development.
# Listen address for the HTTP server (default: :8080)
FOREMAN_ADDR=:8080
# Base URL of the Ollama target (required)
FOREMAN_OLLAMA_URL=http://mac.tail:11434
# Optional bearer token foreman sends to the Ollama target
FOREMAN_OLLAMA_TOKEN=
# Optional bearer token callers must present to foreman
FOREMAN_TOKEN=
# Always-resident embedder model (e.g. nomic-embed-text, qwen3-embedding:0.6b)
FOREMAN_EMBED_MODEL=nomic-embed-text
# Path to the SQLite database file (default: foreman.db)
FOREMAN_DB_PATH=foreman.db
# How often to poll the target's /api/tags (default: 30s)
FOREMAN_POLL_INTERVAL=30s
# Optional HMAC key for signing webhook payloads (ADR-0005)
FOREMAN_WEBHOOK_SECRET=