novox/mesh-lab
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Genesis reads the registry's and the builder's manifests from the catalogue, not the control plane's

Browse Source 
The control plane's manifest comes out of the build the installer runs (novox/hq ADR
0069, 04-ISSUES/072); the catalogue no longer holds a copy, and a bed that demanded
one would stop a genesis that is about to succeed.
This commit is contained in:
jschoubben
2026-09-21 19:23:44 +02:00
parent c8c3028f38
commit 6083b9310a
3 changed files with 11 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -2
View File
@@ -151,9 +151,10 @@ export MESH_LAB_BUILDER=<mesh-controller>/build/mesh-builder # build/, which i
export MESH_LAB_BOOTSTRAP_BINARY=<mesh-host>/mesh-bootstrap
export MESH_LAB_CONTROL_IMAGE=mesh-controller:development # optional; what it carries
# A checkout of the mesh's catalogue. The installer reads the registry's and the control plane's
# A checkout of the mesh's catalogue. The installer reads the registry's and the builder's
# manifests from a copy of it ON THE MACHINE, because at genesis there is no forge, no build
# machine and — until the registry is up — nothing serving anything.
# machine and — until the registry is up — nothing serving anything. The control plane's manifest
# is not among them: it comes out of the build the installer runs (novox/hq ADR 0069).
export MESH_LAB_CATALOG=<mesh-catalog>/modules
# Built with `go build -o <path> ./examples/<name>` in mesh-controller.