mesh-controller

Files

T

History

jschoubben 70341cfbc7 The bus account has JetStream, and the control plane's client has its own inbox

Two refusals the first live connections met. A user in the MESH account was told
"JetStream not enabled for account" the first time it bound a consumer: with
accounts defined, JetStream is enabled per account, not only globally — the
account's setting, which the mesh owns, not the server's block, which it does not.
And the control plane's client used a random inbox prefix where it is granted
exactly _INBOX.<its user>.>, so the server's first answer could not reach it. The
prefix now follows from the user in the URL, for every principal that dials so.

2026-09-28 01:40:10 +02:00

broker

The bus account has JetStream, and the control plane's client has its own inbox

2026-09-28 01:40:10 +02:00

builder

builder: a clone may offer the forge's credential, through git's own store

2026-09-25 21:47:32 +02:00

catalogue

The move mints every credential and tells each machine its membership

2026-09-28 00:16:24 +02:00

envfile

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