Files
mesh-lab/scenarios/postgres-node.yml
T
jschoubben 5d6e8fbe7a Rename mesh-control -> mesh-controller, substrate -> foundation
One name per thing, per the HQ glossary: the module/container/image/binary/repo
becomes mesh-controller, the seat the-controller, and the store+broker pair the
foundation (embedded base bundles, default template and example lock renamed with
their go:embed directives). No behaviour change — a pure vocabulary rename.

Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
2026-09-16 18:40:40 +02:00

30 lines
933 B
YAML

# One machine that becomes a mesh and grants a consumer a database from an assigned postgres provider.
#
# The redis mesh-grant bed proves the whole provider/consumer contract for a cache; this proves it for
# a database (novox/hq ADR 0052/0053): postgres's runtime carries psql, its provisioner creates a role
# and database under the login the mesh derived with the password the mesh minted, and a consumer
# connects to its own database with only what the mesh delivered.
scenario: postgres-node
segments:
hosting:
kind: public
cidr: [192.0.2.0/24]
machines:
anchor:
at: { segment: hosting, address: [192.0.2.10] }
egress: true
inbound: allow
memory: 3GiB
cpus: 2
images:
- mesh-controller:development
# postgres's runtime, built by scripts/build-module-runtime.sh postgres (it carries psql), loaded
# onto the machine.
- mesh-runtime-postgres:development
place:
all: [host, runtime]