73cd6b7aae
Some checks failed
PR build (required check) / changes (pull_request) Successful in 26s
secrets-guard / encrypted (pull_request) Successful in 10s
shell-lint / shellcheck (pull_request) Failing after 14s
PR build (required check) / validate-observability (pull_request) Successful in 1m5s
PR build (required check) / build-frontend (pull_request) Successful in 3m47s
PR build (required check) / build-backend (pull_request) Successful in 4m44s
PR build (required check) / gate (pull_request) Successful in 6s
Docker on the LAN box is the snap package, sandboxed to $HOME (plus a short allowlist) -- it can't see /etc/thermograph.env at all, so env_file: /etc/thermograph.env silently loads nothing for every container there, no matter how correctly the vault renders. Confirmed directly: `docker run --env-file /etc/thermograph.env` fails with "no such file or directory" on a file the shell reads fine; the same file under $HOME loads correctly. render-secrets.sh gains an opt-in second write (THERMOGRAPH_SECRETS_ENV_FILE_MIRROR), deploy-dev.sh points it at infra/deploy/dev-secrets.env (gitignored, re-rendered every deploy), and docker-compose.dev.yml adds it as a second env_file entry for backend/daemon/lake -- compose appends env_file lists across overlays, so this is additive and prod/beta (which never set the mirror var) are unaffected.
72 lines
3.5 KiB
YAML
72 lines
3.5 KiB
YAML
# Dev overlay for the LAN dev server (deploy/deploy-dev.sh):
|
|
#
|
|
# docker compose -f docker-compose.yml -f docker-compose.dev.yml up -d
|
|
#
|
|
# Split-repo adaptation: the monorepo's docker-compose.dev.yml (see
|
|
# thermograph/docker-compose.dev.yml) overlaid a base file where backend and
|
|
# frontend had `build: .` -- dev's whole point there was `--build` in place from
|
|
# the working checkout. This infra repo holds no Dockerfile at all (each service's
|
|
# lives in its own app repo, thermograph-backend / thermograph-frontend), so the
|
|
# base docker-compose.yml already has NO `build:` for either service, only
|
|
# `image: .../${BACKEND_IMAGE_PATH}:${BACKEND_IMAGE_TAG}` (and the frontend
|
|
# equivalent) -- same registry-pull model as prod/beta, just pointed at a dev tag
|
|
# by deploy-dev.sh. This overlay must NOT reintroduce `build:`; it only relaxes
|
|
# resource caps and LAN-exposes a port, same as the monorepo overlay did.
|
|
#
|
|
# Differences from the prod stack (unchanged intent from the monorepo overlay):
|
|
# 1. backend is published on ALL interfaces (0.0.0.0:8137), not loopback, so
|
|
# phones and other devices on the Wi-Fi can reach the dev server directly --
|
|
# dev has no Caddy in front (prod does, which is why the base file binds
|
|
# 127.0.0.1 only).
|
|
# 2. frontend's port publish is dropped entirely -- dev has no Caddy to reach it
|
|
# directly, so it stays compose-internal-only, reached solely through
|
|
# backend's own reverse-proxy fallback (THERMOGRAPH_FRONTEND_BASE_INTERNAL,
|
|
# see backend/web/app.py's _proxy_to_frontend in the backend repo). This
|
|
# keeps the dev stack serving the one URL it always has, at :8137.
|
|
# 3. The CPU caps are removed -- dev runs UNCAPPED (no thread/CPU limits), unlike
|
|
# prod's backend=4 / frontend=2 / db=2 allocation. `!reset` drops the base
|
|
# value (both the top-level `cpus:` and the Swarm-style `deploy.resources`
|
|
# block the base file carries for parity).
|
|
# 4. backend/daemon/lake get a second env_file entry pointing at a copy of the
|
|
# render under $APP_DIR (deploy-dev.sh sets THERMOGRAPH_SECRETS_ENV_FILE_MIRROR
|
|
# to produce it). This box's Docker is the snap package, confined to $HOME --
|
|
# it can't see /etc/thermograph.env at all (not a permissions error, it just
|
|
# doesn't exist as far as snap-confined Docker is concerned), so the base
|
|
# file's env_file entry silently loads nothing here. compose appends env_file
|
|
# lists across overlays (last-wins on duplicate keys), so this is additive:
|
|
# prod/beta never set the mirror var, so they only ever get the base entry.
|
|
services:
|
|
backend:
|
|
ports: !override
|
|
- "8137:8137"
|
|
cpus: !reset null
|
|
deploy: !reset null
|
|
env_file:
|
|
- path: ./deploy/dev-secrets.env
|
|
required: false
|
|
frontend:
|
|
ports: !reset null
|
|
cpus: !reset null
|
|
deploy: !reset null
|
|
# Same uncapped-on-dev treatment for the daemon; it has no ports to touch
|
|
# (outbound-only in every environment).
|
|
daemon:
|
|
cpus: !reset null
|
|
deploy: !reset null
|
|
env_file:
|
|
- path: ./deploy/dev-secrets.env
|
|
required: false
|
|
db:
|
|
cpus: !reset null
|
|
deploy: !reset null
|
|
lake:
|
|
cpus: !reset null
|
|
deploy: !reset null
|
|
# Uncapped memory on dev too (prod ceilings it at 8g). The Postgres/DuckDB
|
|
# memory *budget* is still the ~8 GB derived by deploy/db/init/20-tuning.sh from
|
|
# the default DB_MEMORY (raise DB_MEMORY to give dev more); shm_size stays (it's
|
|
# required shared memory for parallel query, not a limit).
|
|
mem_limit: !reset null
|
|
env_file:
|
|
- path: ./deploy/dev-secrets.env
|
|
required: false
|