jschoubben
86ea181c76
Thirty modules the mesh builds, provisions and runs, as manifests — one per module, flat under modules/. They were in mesh-control/examples/, which framed the mesh's real modules as illustrations of a control-plane package; they are neither examples nor the control plane's. The engine that reads them stays in mesh-control; the data lives here, consumed as a build source. Answers the tier-4 question novox/hq ADR 0030 left open — where the catalogue lives — in favour of one flat repository, which the drop of domain grouping (seats, claims and tags instead) makes the right shape. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF
40 lines
773 B
JSON
40 lines
773 B
JSON
{
|
|
"module": "nodered",
|
|
"version": "1",
|
|
"capabilities": [
|
|
"container-runtime"
|
|
],
|
|
"listens": [
|
|
{
|
|
"port": 1880,
|
|
"protocol": "tcp",
|
|
"from": "mesh",
|
|
"why": "the flow editor and the endpoints flows expose"
|
|
}
|
|
],
|
|
"resources": [
|
|
{
|
|
"id": "data",
|
|
"type": "directory",
|
|
"path": "/services/nodered/data",
|
|
"mode": "0700",
|
|
"owner": "1000:1000"
|
|
},
|
|
{
|
|
"id": "server",
|
|
"type": "container",
|
|
"name": "nodered",
|
|
"image": "nodered/node-red@sha256:02a2b92a41b73d2bc388238b86e4fcaab7fb5466373adb24e1df6aa5845265ff",
|
|
"env": {
|
|
"TZ": "Etc/UTC"
|
|
},
|
|
"ports": [
|
|
"1880"
|
|
],
|
|
"volumes": [
|
|
"/services/nodered/data:/data"
|
|
]
|
|
}
|
|
]
|
|
}
|