2026-07-22 18:57:02 +00:00
|
|
|
# Local docker-compose overrides. Copy to .env (gitignored) for `docker compose
|
2026-07-26 06:56:38 +00:00
|
|
|
# up` / `make up` on a laptop: cp .env.example .env
|
2026-07-22 18:57:02 +00:00
|
|
|
#
|
|
|
|
|
# Compose auto-reads a repo-root .env for ${VAR} interpolation in
|
2026-07-26 06:56:38 +00:00
|
|
|
# docker-compose.yml. On the fleet (dev/beta/prod), these values live in each
|
|
|
|
|
# environment's own rendered env file instead (/etc/thermograph.env,
|
|
|
|
|
# /etc/thermograph-beta.env — see deploy/secrets/README.md), so this file is
|
|
|
|
|
# only for a local, unmanaged run.
|
2026-07-22 18:57:02 +00:00
|
|
|
|
|
|
|
|
# Database password. Compose uses it to initialize the postgres container AND to
|
|
|
|
|
# build the app's THERMOGRAPH_DATABASE_URL. Change it before first `up`.
|
|
|
|
|
POSTGRES_PASSWORD=change-me
|
|
|
|
|
|
daemon: move the Discord gateway and scheduler out of the web process into Go (#21)
The gateway bot and APScheduler were long-lived stateful I/O loops running
inside the async web app under a leader election. They move into a single Go
binary that owns ONLY that I/O -- websocket, RESUME, heartbeat, backoff, timers.
It owns no grading logic. Anything needing data calls back over a new
internal-only surface (/internal/discord/grade, /internal/jobs/*). Grading
depends on polars and the parquet cache; reimplementing it in Go would let the
bot's grades drift from the API's. The grade route returns gateway-ready JSON
and Go relays the bytes verbatim.
The binary ships in the backend image and runs as a second compose service off
the same tag, so the two ends of the /internal/* contract can never skew.
deploy.sh rolls daemon alongside backend -- without that the service would never
be created, since a single-service deploy uses --no-deps. It also probes the
image first and skips the daemon when rolling a tag that predates the binary:
infra tracks main while image tags are env-staged, so a host can legitimately be
asked to roll an older backend image, and creating the service anyway would
leave a container crash-looping on a missing binary.
replicas: 1 with order: stop-first replaces the leader election -- Discord
permits one gateway connection per bot token.
THERMOGRAPH_INTERNAL_TOKEN is optional: both ends derive it from
THERMOGRAPH_AUTH_SECRET via HMAC under a domain-separation label, so this needs
no new vault entry. The derivation is pinned to a shared cross-language test
vector asserted on both sides, so drift fails CI instead of 401ing every call.
Fail closed when neither secret is set.
Improvements over the Python: a close intended for RESUME uses 4000 rather than
1000 (Discord invalidates a session closed 1000, so the old default defeated its
own resume); MESSAGE_CREATE runs on a bounded worker pool; and a malformed HELLO
returns an error rather than a clean reconnect, which would otherwise reset
backoff and hot-loop against the gateway.
365 Python tests pass; Go build/vet/test -race clean; shellcheck 0 findings.
2026-07-23 22:49:54 +00:00
|
|
|
# OPTIONAL. Shared secret between the daemon service (Discord gateway + job
|
|
|
|
|
# timers) and the backend's /internal/* routes.
|
|
|
|
|
#
|
|
|
|
|
# Leave it empty and both ends DERIVE the same token from THERMOGRAPH_AUTH_SECRET
|
|
|
|
|
# (HMAC-SHA256 under a fixed label), which every environment already provisions —
|
|
|
|
|
# so the daemon needs no new vault entry and no operator step. Set it only to
|
|
|
|
|
# override that, e.g. to rotate this surface independently of the auth secret:
|
|
|
|
|
# openssl rand -hex 32
|
|
|
|
|
#
|
|
|
|
|
# With neither this nor THERMOGRAPH_AUTH_SECRET set, both ends fail closed: the
|
|
|
|
|
# backend disables the internal routes and the daemon refuses to start. Never
|
|
|
|
|
# routed publicly — Caddy only forwards /api/*, /digest and
|
|
|
|
|
# /discord/interactions to the backend.
|
|
|
|
|
THERMOGRAPH_INTERNAL_TOKEN=
|
|
|
|
|
|
2026-07-22 18:57:02 +00:00
|
|
|
# --- Everything below is optional -- docker-compose.yml already defaults each
|
|
|
|
|
# --- of these, so a plain `make up` works with none of it set. Uncomment to
|
|
|
|
|
# --- override.
|
|
|
|
|
|
|
|
|
|
# TimescaleDB image tag. Defaults to the floating latest-pg18 tag. Pin it to an
|
|
|
|
|
# exact minor (e.g. 2.17.2-pg18) before any host of this stack could ever
|
|
|
|
|
# replicate with another -- see docker-compose.yml's db service comment.
|
|
|
|
|
# TIMESCALEDB_TAG=latest-pg18
|
|
|
|
|
|
2026-07-26 06:56:38 +00:00
|
|
|
# Postgres sizing. Only meaningful for an environment that runs its OWN db
|
|
|
|
|
# service — dev's compose stack (this file) and prod's Swarm stack, which
|
|
|
|
|
# sizes the ONE shared TimescaleDB instance on vps2 (see
|
|
|
|
|
# deploy/secrets/prod.yaml, currently DB_MEMORY=16g). Beta shares that same
|
|
|
|
|
# instance rather than running a second one, so a DB_MEMORY/DB_CPUS value in
|
|
|
|
|
# beta's own vault file no longer sizes anything — don't be misled by its
|
|
|
|
|
# presence there. Local/dev default to 8g / 2 CPUs.
|
2026-07-22 18:57:02 +00:00
|
|
|
# DB_MEMORY=8g
|
|
|
|
|
# DB_CPUS=2
|
|
|
|
|
|
|
|
|
|
# Backend uvicorn worker count and CPU cap. Terraform raises these on bigger
|
|
|
|
|
# hosts; defaults keep a plain `docker compose up` identical to before.
|
|
|
|
|
# WORKERS=4
|
|
|
|
|
# APP_CPUS=4
|
|
|
|
|
|
|
|
|
|
# Frontend CPU cap.
|
|
|
|
|
# FRONTEND_CPUS=2
|
|
|
|
|
|
|
|
|
|
# Registry + per-service image path/tag. Local dev normally builds each image
|
|
|
|
|
# in its own app repo (thermograph-backend / thermograph-frontend) tagged
|
|
|
|
|
# :local, which is the default here -- only set these to pull a specific
|
|
|
|
|
# published build instead of building locally.
|
|
|
|
|
# REGISTRY_HOST=git.thermograph.org
|
|
|
|
|
# BACKEND_IMAGE_PATH=emi/thermograph-backend/app
|
|
|
|
|
# BACKEND_IMAGE_TAG=local
|
|
|
|
|
# FRONTEND_IMAGE_PATH=emi/thermograph-frontend/app
|
|
|
|
|
# FRONTEND_IMAGE_TAG=local
|
