5 Commits

Include renames

Author	SHA1	Message	Date
ginnoir	1028bc3a74	Serve 5etools from storage1 via Caddy instead of a 14G image. ... The mirror is static files; keeping it in a container burned root disk. Caddy file_server bind-mounts /storage1/labdata/5etools like the other static sites.	2026-08-25 22:24:39 -05:00
ginnoir	7aa95fa00a	refactor: pure env_file stack.env convention across all stacks ... Every service now reads stack.env via env_file with container-exact var names — no ${VAR} parse-time interpolation, no Portainer UI env vars (except stacks/dev, kept on UI-env interpolation as documented exception). - media: drop PUID/PGID/TZ env lines (env_file covers); resolve ${ROOT} - foundry: secrets via env_file; FOUNDRY_PATCH_URLS -> CONTAINER_PATCH_URLS - monitoring: HOMARR_SECRET_ENCRYPTION_KEY -> SECRET_ENCRYPTION_KEY - notify: FRESHRSS_USER composed in stack.env; TZ via env_file - owncloud: container-exact OWNCLOUD_*/MYSQL_* keys; runtime $$ healthcheck - resume/famapp: composites (DATABASE_URL etc.) written out in stack.env - authentik: container-exact keys; image tag pinned in compose - notes: couchdb creds via env_file - remote: gains stack.env (no secrets; convention completeness) - CLAUDE.md: env convention, valhalla-lab registration-only note, correct on-host Portainer working-copy path (/config/portainer/compose/<id>) Validated with docker compose config on valhalla for all 15 stacks.	2026-06-09 16:03:47 -05:00
ginnoir	1e2970d220	chore: add env_file: stack.env to all compose services ... Portainer git-stack deployments require an explicit env_file reference in the compose file to load variables from the repo's stack.env. Adds env_file: [stack.env] before every service-level environment: block across all 10 stacks.	2026-06-04 22:11:51 -05:00
ginnoir	b7f51524d9	fix(foundry): disable dead plutonium patch gist (404 -> crash/backoff loop)	2026-06-04 17:04:12 -05:00
ginnoir	57cd6ed270	refactor: split monolith into per-domain stacks (Phase A: build) ... Add stacks/<domain>/ compose + env for the 11 target stacks (proxy, media, foundry, owncloud, resume, famapp, authentik, notify, monitoring, remote, dev). Each app stack joins a shared external `edge` network for Caddy and keeps its DB/cache co-located (no shared backing services). All named volumes convert to tiered bind mounts: DBs/configs -> /config (SSD), blobs/repos/registry -> /storage1/labdata (ZFS). Gitea repos+LFS split to ZFS. Move Vault into the management plane (portainer-compose.yml) and add the shared `edge` network there. apply-compose.ps1 -Portainer now also pushes vault.hcl. Additive only: root docker-compose.yml/.env/Caddyfile untouched, so the live monolith is unchanged. Live cutover (Phase B) is next.	2026-06-04 16:11:31 -05:00