# One machine that becomes a mesh and is then assigned a SECOND wave of modules at once — the ones # converted this session (novox/hq ADR 0039/0048/0052): mongodb, unifi and marrytts, with postgres # carried along as a known-good control. This is catalogue-small's sibling: same first-node foundation, # same one-push co-residence, a different (and heavier) set of modules. # # The four exercise the three converted shapes: # - mongodb — a database PROVIDER shaped like postgres (server + a broker-bound runtime carrying # `mongosh`, the runtime running the provisioner over the ADR-0048 MESH_RECEIVES contract). # - unifi — a tooled APP (server + a broker-bound runtime that serves tools; no provisioner), # shaped like plex. # - marrytts — a manifest-only PLAIN container: no runtime, no tools, it only has to come up. # - postgres — the known-good provider control, verbatim from catalogue-small. # # None of the four share a directory, so the shared-workspace refusal (novox/hq 04-ISSUES/012) does # not bite; 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 {mongodb,unifi,postgres} build the runtime images into the local # daemon (mongodb carries mongosh; unifi and postgres carry their CLIs). The service images # (mongo, unifi-controller, marytts, postgres) must be in the local daemon to be stocked. scenario: catalogue-apps 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 past catalogue-small's 6GiB: this wave carries two heavy JVM/embedded-DB service # containers (the UniFi controller and MaryTTS) on top of the foundation, mongodb, postgres and # three node runtimes — a dozen containers, two of them memory-hungry at startup. memory: 8GiB cpus: 4 images: - mesh-controller:development # The runtimes built by scripts/build-module-runtime.sh and stocked here. marrytts needs none. - mesh-runtime-mongodb:development - mesh-runtime-unifi:development - mesh-runtime-postgres:development place: all: [host, runtime]