# One machine that becomes a mesh and is then assigned FOUR modules at once — the first bed that # proves multi-module co-residence (the migration-rehearsal shape, novox/hq 04-ISSUES/012 context). # # The per-backend beds each assign one module: postgres (a database provider), minio (an object-store # provider), redis (a cache provider + tools), plex (a tools module). This raises the same first-node # foundation and then assigns all four to the one anchor in a single push, so the proof is that they # resolve and come up TOGETHER on one node — nothing new about any single module, everything new about # their co-residence. # # The four are chosen because none of them share a directory, so the shared-workspace refusal # (novox/hq 04-ISSUES/012 — the media stack) does not bite here; that class stays for a later bed. # # MESH_LAB_HOST_BINARY=.../mesh-host MESH_LAB_BUNDLE=.../examples/foundation-first-node.lock # scripts/build-module-runtime.sh {postgres,redis,minio,plex} build the four runtime images into the # local daemon (postgres carries psql, minio carries mc), which this scenario stocks and serves by # the internet over its uplink. Only the mesh's own images come from the local daemon. scenario: catalogue-small segments: hosting: kind: public cidr: [192.0.2.0/24] machines: anchor: at: { segment: hosting, address: [192.0.2.10] } egress: true inbound: allow # Sized up: this anchor runs the foundation (store, broker, control) plus four modules — three of # which are a server container and a runtime container each — so a dozen containers at once. The # single-module beds run at 3GiB; co-residence needs the headroom. memory: 6GiB cpus: 4 images: - mesh-controller:development # The four per-module runtimes, built by scripts/build-module-runtime.sh and stocked here. plex # needs no server image in the lab — its runtime serves tools with no Plex to reach. - mesh-runtime-postgres:development - mesh-runtime-redis:development - mesh-runtime-minio:development - mesh-runtime-plex:development place: all: [host, runtime]