Join the proxy network for Nginx Proxy Manager access

- docker-compose.yml now attaches the toolkit's container to the
  external 'proxy' Docker network, the same one NPM already uses to
  reach Work Package Suite's internal nginx container by name
  (confirmed via NPM's generated proxy_host/11.conf).
- Document the exact NPM Proxy Host setup for MVP.controls.dev in
  PORTAINER_DEPLOY.md.
- Update CHANGELOG.
This commit is contained in:
2026-09-23 16:07:27 -07:00
parent 6baf908cf9
commit 2e8d699a36
3 changed files with 33 additions and 5 deletions

View File

@@ -1,10 +1,10 @@
# Standalone compose file for this tool.
#
# To run it alongside the Work Package Suite container instead, copy the
# "sde-meeting-toolkit" service block below into that stack's compose file.
# Put it on the same network as the other services only if you want
# hostname-based access between containers; this tool does not call the
# Work Package Suite API and does not need that network to function.
# Joins the "proxy" Docker network so Nginx Proxy Manager can reach this
# container by name (sde-meeting-toolkit) the same way it reaches Work
# Package Suite's own internal nginx container. "proxy" must already exist
# on the host; it is not created here (external: true), since NPM's own
# stack owns it.
services:
sde-meeting-toolkit:
build: .
@@ -26,3 +26,9 @@ services:
# Persists the per-user token quota file across restarts and rebuilds.
# Without this, everyone's daily usage silently resets on every deploy.
- ./data:/app/data
networks:
- proxy
networks:
proxy:
external: true