vh
c5beeac32d
Homepage on esh-docker-vm:5100 was the one stack whose config lived only on the host, edited in place. Its version history was six hand-rolled services.yaml.bak-* files. Now canonical here and deployed with deploy-stack.sh like everything else; the .bak files are gone. Corrections from the audit: - ANA-Firewall described a 'Fortigate 81F'. It is a FortiGate-80F running FortiOS 7.2.10, verified live against the device. - NH3-Ansible pointed at 10.100.50.42 as an 'Ansible control node'. That host is nh3-extdev, the manager/external-dev successor after nh3-ansible was retired. Renamed and re-described. - Dropped the UltraSeedbox layout group: nothing provides it, so it only ever rendered empty. Adds .env.example and a README documenting the two-path service model (docker label discovery across five engines vs manual entries), the labels-only-apply- on-recreate rule, and the foot-guns found: HOMEPAGE_ALLOWED_HOSTS matches host AND port so a bare IP does not cover IP:port; :2375 is plaintext and unauthenticated on all five engines; ping: cards can only be judged from the dashboard host. Verified after deploy via /api/services: 105 cards across 19 groups, both corrections live, ana-docker discovery intact.
14 lines
672 B
Bash
14 lines
672 B
Bash
# homepage — tunables. Real .env lives on esh-docker-vm at
|
|
# /opt/docker/compose/homepage/.env and is NEVER committed.
|
|
|
|
# Host validation. Homepage matches the Host header INCLUDING THE PORT, so a
|
|
# bare IP does NOT cover the IP:port form -- `10.0.50.45` alone still rejects
|
|
# http://10.0.50.45:5100/ with "Host validation failed". List every host:port
|
|
# combination the dashboard is actually reached by.
|
|
HOMEPAGE_ALLOWED_HOSTS=eshhome,eshhome.esteban.net,10.0.50.45,10.0.50.45:5100,localhost:5100
|
|
|
|
# Media widget API keys — referenced from services.yaml as
|
|
# {{HOMEPAGE_VAR_PLEX_KEY}} / {{HOMEPAGE_VAR_JELLYFIN_KEY}}
|
|
HOMEPAGE_VAR_PLEX_KEY=
|
|
HOMEPAGE_VAR_JELLYFIN_KEY=
|