novox/mesh-networking

Fork 0

T

jschoubben ccfdaec5ed

mesh/delivery merged: source.main moved to novox/mesh-networking@9be2faaf8b00

Details

mesh/delivery-group group feat/47-G-join12 merged: every member is merged

Details

mesh/check checking ccfdaec5ed2d on 9be2faaf8b00 | novox/mesh-networking#6 in group feat/47-G-join12

Round 2 T2, T5: mesh-wireguard and route-proxy end G with their merge-base test counts; roles in the test

The two tests G added fold into existing ones as subtests (design 47 G §626); route-proxy's provider test names
a role, not a node (T5).

Builds: design 47 G §626, A-306; review round 2 findings T2, T5
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h

2026-11-12 22:20:32 +01:00

modules

Round 2 T2, T5: mesh-wireguard and route-proxy end G with their merge-base test counts; roles in the test

2026-11-12 22:20:32 +01:00

.gitignore

Move route-proxy out of the controller's repository, which is archived with the controller

2026-11-02 11:45:17 +01:00

README.md

Move route-proxy out of the controller's repository, which is archived with the controller

2026-11-02 11:45:17 +01:00

README.md

mesh-networking

Novox Mesh — networking: the modules that carry traffic into and across the mesh, each under modules/<name> with its own manifest (module.json) and Go module.

route-proxy provides route: the public HTTP and HTTPS entry, serving each name a consumer asks for from the seat mesh-provisioner's plans (its README says how). It moved here from the controller's repository, history kept, when the controller was removed (issue 1126).

Made by the mesh from the gitea module's config value repositories (novox/hq ADR 0428). Main takes no push: a change reaches it by a pull request whose mesh/check passed and the operator approved.