Files

T

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

route-proxy provides `route` to five modules and lived in novox/mesh-controller, archived once the controller is
removed (issue 1126). Its history comes along (git filter-repo of modules/route-proxy and its earlier home
examples/route-proxy). Its contract's Go module path names this repository, and route-proxy builds the contract from
its own tree through a replace, so no tag is needed before the first build. The two manifest tests that held its
public ACME account and mounted program lived in the controller's internal/ownmanifest; they move beside the module.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

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

668 B

Raw Blame History

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.

668 B Raw Blame History

mesh-networking

668 B

Raw Blame History