11 modules: a container's ports say the software's port, not the machine's #53

2026-09-24T13:46:10Z

jschoubben commented

2026-09-24 13:46:10 +00:00

Fixes hq issue 091 (measured 2026-09-22: 14 of 46 modules hardcode a machine-side port in their own manifest). ADR 0038 already says the mesh assigns it, and the machinery already exists (PortFor, publishedOn) — these modules just never complied.

Stripped to the bare software port in 11 of them: de-spiegel, gitea, hello-web, mailu, mssql, n8n, novox.be, only-office, photos, photos-eef, photos-filip. Left the two defensible kinds untouched: postgres/lavinmq/distribution (foundation, genesis-rewritten) and unifi (protocol-fixed, device discovery).

gitea was live, not just tidiness — its manifest said 2222:22 but the actual adopted container runs on 222. Harmless while held, but the next take would have broken SSH git access. Recorded 222 as novox's own node setting for it, applied and pushed already (no container disruption — confirmed both gitea and mesh-gitea untouched).

hq companion PR marks ADR 0038 accepted and closes issue 091.

Fixes hq issue 091 (measured 2026-09-22: 14 of 46 modules hardcode a machine-side port in their own manifest). ADR 0038 already says the mesh assigns it, and the machinery already exists (`PortFor`, `publishedOn`) — these modules just never complied. Stripped to the bare software port in 11 of them: `de-spiegel`, `gitea`, `hello-web`, `mailu`, `mssql`, `n8n`, `novox.be`, `only-office`, `photos`, `photos-eef`, `photos-filip`. Left the two defensible kinds untouched: `postgres`/`lavinmq`/`distribution` (foundation, genesis-rewritten) and `unifi` (protocol-fixed, device discovery). `gitea` was live, not just tidiness — its manifest said `2222:22` but the actual adopted container runs on `222`. Harmless while held, but the next `take` would have broken SSH git access. Recorded `222` as `novox`'s own node setting for it, applied and pushed already (no container disruption — confirmed both `gitea` and `mesh-gitea` untouched). hq companion PR marks ADR 0038 `accepted` and closes issue 091.

jschoubben added 1 commit 2026-09-24 13:46:10 +00:00

11 modules: a container's ports say the software's port, not the machine's 12f885ffc5

hq issue 091, measured 2026-09-22: 14 of 46 modules with containers fix the
machine side of a published port in their own manifest -- a fact about one
machine (which port HAL happened to publish it on) written into a
definition meant for any node. ADR 0038 already says the mesh assigns the
machine side and a module says only what it needs; the machinery already
does it (internal/inventory/ports.go's PortFor, declaration.go's
publishedOn rewrites a bare port automatically). These 14 just never
complied.

Fixed 11 of them -- stripped to the bare software port, letting assignment
take over: de-spiegel, gitea, hello-web (the demo module), mailu, mssql,
n8n, novox.be, only-office, photos, photos-eef, photos-filip.

Left alone, the two defensible kinds the issue names: postgres/lavinmq/
distribution (foundation, genesis-rewritten per ADR 0100 -- the number in
the manifest is a default, not a claim) and unifi (protocol/
device-discovery fixes the number; nothing else can find the controller).

gitea was a live one, not just a tidiness fix: its manifest said 2222:22,
but the actual adopted, running container is on 222. Harmless while held,
but the next 'take' would have recreated it on the wrong port and broken
SSH git access. Recorded 222 as novox's own setting for it (settings set
gitea -node novox) so that doesn't happen.

jschoubben merged commit 3e8ecfa4eb into main

2026-09-24 13:53:34 +00:00

jschoubben deleted branch fix/091-ports-machine-side-is-the-mesh-to-assign

2026-09-24 13:53:34 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#53