novox/mesh-controller
6
0
Fork 0
Code Issues Pull Requests 5 Releases Wiki Activity
Files
8b016cc62b23b77b283751da73c56f49a76b438e
mesh-controller/internal
T
History
jochen 8b016cc62b A Go tools bundle is served by its binary (hq ADR 0193) 
A bundle compiled to a binary has no entrypoints, and loads had to name one, so a Go bundle could
not be served. Its binary is what the runtime starts: loads names the binary, derived when the
module lists tools, and the runtime is told the binary's path, delivered like any tools bundle.
2026-10-03 22:27:01 +02:00
..
broker
The controller announces as the tool runtimes do, and answers $SRV.STATS (hq ADR 0197)
2026-10-03 22:18:27 +02:00
builder
A runtime compiled to a binary runs itself (hq ADR 0193)
2026-10-03 21:24:12 +02:00
catalogue
A Go tools bundle is served by its binary (hq ADR 0193)
2026-10-03 22:27:01 +02:00
envfile
An address is read from the node's settings where it is used, never recorded with a port
2026-09-23 23:49:31 +02:00
identity
Adopt the tunnel as a mesh fact, refuse a mismatched takeover, and rekey after enrolment
2026-09-24 00:02:07 +02:00
inventory
A bundle stands on the toolchain it is compiled in (hq issue 211)
2026-10-03 22:18:20 +02:00
licences
Rename mesh-control -> mesh-controller, substrate -> foundation
2026-09-16 18:40:40 +02:00
link
A bundle stands on the toolchain it is compiled in (hq issue 211)
2026-10-03 22:18:20 +02:00
overlay
The roster is the machines: each node's internal domain covers its routes (hq ADR 0191)
2026-10-03 16:10:16 +02:00
secrets
A provider with one credential shares it with every consumer, remade for all at once (hq ADR 0158)
2026-10-01 12:26:44 +02:00
store
The control plane's own manifest says where the node put the store and the broker
2026-09-23 23:49:55 +02:00
token
Record whether a node is adopted and which modules were taken on it (hq ADR 0100)
2026-09-22 17:14:05 +02:00