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

@@ -63,3 +63,19 @@ Setting up a Gitea webhook to trigger this automatically is possible later, but
## The data folder
`docker-compose.yml` mounts `./data:/app/data` so the per-user token quota file survives a restart, if that feature is ever turned back on. Portainer creates this folder under the stack's own directory on the host. With `TOKEN_LIMIT_PER_USER=0`, nothing is written there today; the mount is harmless and already in place for when it's needed.
## Giving it a real address through Nginx Proxy Manager
`docker-compose.yml` joins the toolkit's container to a Docker network named `proxy`. This is the same network Nginx Proxy Manager (NPM) uses to reach Work Package Suite's own internal nginx container by name. The `proxy` network must already exist on the host before you deploy this stack; `docker-compose.yml` does not create it (`external: true`), it only joins it.
1. Deploy or redeploy the `sde-meeting-toolkit` stack as described above. Confirm in Portainer that the container is attached to the `proxy` network (check the container's network list).
2. Open NPM's own web admin UI (not Portainer). This is a separate address, usually the Docker host's IP or hostname on port `81`, for example `http://<host>:81`.
3. Go to **Hosts** > **Proxy Hosts** > **Add Proxy Host**.
4. Set **Domain Names** to `MVP.controls.dev`.
5. Set **Scheme** to `http`.
6. Set **Forward Hostname / IP** to `sde-meeting-toolkit`. NPM resolves this by Docker container name over the shared `proxy` network, the same way it resolves Work Package Suite's `nginx_webserver`.
7. Set **Forward Port** to `5173`.
8. On the **SSL** tab, request a new Let's Encrypt certificate for `MVP.controls.dev`, the same way the existing `wp.controls.dev` host is set up.
9. Save. Confirm `MVP.controls.dev` loads the toolkit's landing page in a browser.
DNS for `MVP.controls.dev` must point at the same address the existing `wp.controls.dev` record points at, so it reaches this Docker host and NPM. If that record does not already exist, it needs to be added wherever `controls.dev`'s DNS is managed, before step 9 will succeed.