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

@@ -2,6 +2,12 @@
All notable changes to this project are logged here, newest first. This file starts from the point the toolkit was handed off and set up in this repo.
## 2026-09-23
- Added: joined the toolkit's Docker container to the `proxy` network, the same shared network Nginx Proxy Manager already uses to reach Work Package Suite's internal nginx container by name. Confirmed by reading NPM's own generated config for `wp.controls.dev` (`/data/nginx/proxy_host/11.conf`), which forwards to a container named `nginx_webserver`, not an IP address. `docker-compose.yml` now declares `proxy` as an external network and attaches the container to it.
- Added: a "Giving it a real address through Nginx Proxy Manager" section in `PORTAINER_DEPLOY.md`, with the exact NPM Proxy Host settings to point `MVP.controls.dev` at this container.
- Decided: the public address for this toolkit will be `MVP.controls.dev`, a new subdomain, the same pattern as the existing `wp.controls.dev`. Not a sub-path under Work Package Suite's own domain, to avoid base-path complications in the toolkit's code.
## 2026-09-04 (2)
- Added: the two tools now work together. Each tool's header has a link to the other tool. On the Field Problem Workshop, a cluster tagged with a candidate solution (for example "Tracking MVP (pilot)") gets a "Send to Scope Lock" button. Clicking it adds that cluster as a real, unsorted item on the Scope Lock Meeting Suite's Scope Boundary Board. Both tools already share the same browser origin, so this uses a small shared `localStorage` queue; no backend or database was needed. The item lands on Scope Lock's board the next time that tool is opened or refreshed, and re-sending the same cluster will not create a duplicate. Verified with a jsdom test that simulates both tools sharing one browser's storage.