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.
10 lines
472 B
Bash
10 lines
472 B
Bash
# foundry stack secrets — injected into both Foundry services via env_file.
|
|
# Var names are exactly what the felddy/foundryvtt container reads.
|
|
FOUNDRY_USERNAME=ginnoir
|
|
FOUNDRY_PASSWORD=agt-UAU!uky_ykh3juy
|
|
FOUNDRY_ADMIN_KEY=fuckyouben
|
|
# NOTE: the old plutonium patch gist 404s (dead URL), which put Foundry into a
|
|
# crash/backoff loop. Disabled to restore service. To re-enable, set this to a
|
|
# CURRENT raw gist URL for the plutonium patch script.
|
|
CONTAINER_PATCH_URLS=
|