mesh-controller

Files

T

jschoubben c978aa7d64 No container is given the mesh's names; it resolves them

novox/hq ADR 0148, step 3. Every container got the whole roster as
--add-host entries at creation and nothing re-read them (issues 109,
135); once the roster was in the digest so that could be caught, one
name moving anywhere replaced every container in the mesh (issue 151).
A container resolves through its machine's resolver, which the resolver
module tells the runtime about once per machine. A module's own hosts
entries stay exactly as declared.

Also brings the resolver tests up to the catalogue as it now is: the
runtime is reloaded (never restarted) and given live-restore, and the
resolver answers by address, not by interface (issue 110).

2026-09-30 14:38:07 +02:00

broker

A consumer a machine is bound to keeps the subject that works

2026-09-29 23:55:56 +02:00

builder

The linker is told once, not twice

2026-09-30 12:54:29 +02:00

catalogue

No container is given the mesh's names; it resolves them

2026-09-30 14:38:07 +02:00

envfile

An address is read from the node's settings where it is used, never recorded with a port