thermograph/backend/.dockerignore

# Local virtualenvs are disposable dev state (see CLAUDE.md), but without this
# file `COPY . /app/` on a dev checkout ships ~400MB of site-packages the image
# already installs via pip — and the chown -R layer then duplicates it AGAIN.
# CI contexts never contain a .venv, so this only protects `:local` dev builds.
# Do NOT add daemon/ here: the daemon-builder stage COPYs it from this same
# context.
.venv*
__pycache__/
*.py[co]
.pytest_cache/
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			`# Local virtualenvs are disposable dev state (see CLAUDE.md), but without this`
			# file `COPY . /app/` on a dev checkout ships ~400MB of site-packages the image
			`# already installs via pip — and the chown -R layer then duplicates it AGAIN.`
			# CI contexts never contain a .venv, so this only protects `:local` dev builds.
			`# Do NOT add daemon/ here: the daemon-builder stage COPYs it from this same`
			`# context.`
			`.venv*`
			`__pycache__/`
			`*.py[co]`
			`.pytest_cache/`