The forge's own address follows the port the node gave it (hq issue 088) #40

2026-09-22T21:29:42Z

jschoubben commented

2026-09-22 21:29:42 +00:00

Merge this first, before mesh-controller's branch of the same name: its test reads this manifest and asserts the new value.

One token: the forge's own address in its container environment becomes ${port:3000} instead of the literal. On a node that gives the forge another machine port — the control-node must publish 2999, because that is where the predecessor's proxy sends the public name — the address then renders as that port instead of pointing at nothing.

Everything else in this manifest that names 3000 is already correct and already translated: what it listens on, its published mapping, what it serves, and its route contribution.

**Merge this first**, before mesh-controller's branch of the same name: its test reads this manifest and asserts the new value. One token: the forge's own address in its container environment becomes `${port:3000}` instead of the literal. On a node that gives the forge another machine port — the control-node must publish 2999, because that is where the predecessor's proxy sends the public name — the address then renders as that port instead of pointing at nothing. Everything else in this manifest that names 3000 is already correct and already translated: what it listens on, its published mapping, what it serves, and its route contribution.

jschoubben added 1 commit 2026-09-22 21:29:42 +00:00

The forge's sidecar dials the port the machine put the forge on (hq issue 088) cf30d4b3d0

MESH_GITEA_URL named 3000 outright. The forge's container publishes 3000 without
fixing the machine side, so the mesh assigns it — and on a node given that port
as a setting it is the operator's number. The mapping that lets the forge go on
binding 3000 does nothing for a caller dialling the machine's loopback, so the
sidecar dialled a port nothing was listening on wherever the two differed.

${port:3000} is the mesh's answer to exactly that question, and it now resolves
in a container's environment as it always has in a file. The forge declares it
listens on 3000, so it may ask.

Still names 3000: the route contribution (hq issue 089) and the `listens` and
`ports` entries, which are the software's own number and belong there.

jschoubben merged commit d0fed5b982 into main

2026-09-22 21:29:48 +00:00

jschoubben deleted branch feat/forge-address

2026-09-22 21:29:48 +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#40