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
38 lines
793 B
JSON
38 lines
793 B
JSON
{
|
|
"module": "home-assistant",
|
|
"version": "1",
|
|
"capabilities": [
|
|
"container-runtime"
|
|
],
|
|
"listens": [
|
|
{
|
|
"port": 8123,
|
|
"protocol": "tcp",
|
|
"from": "mesh",
|
|
"why": "the dashboard and the API"
|
|
}
|
|
],
|
|
"resources": [
|
|
{
|
|
"id": "config",
|
|
"type": "directory",
|
|
"path": "/services/home-assistant/config",
|
|
"mode": "0700",
|
|
"owner": "1000:1000"
|
|
},
|
|
{
|
|
"id": "server",
|
|
"type": "container",
|
|
"name": "home-assistant",
|
|
"image": "ghcr.io/home-assistant/home-assistant@sha256:14931c6b13756317849f46da1d01b45937a1150db66c081cfe529d48215943fe",
|
|
"network": "host",
|
|
"env": {
|
|
"TZ": "Etc/UTC"
|
|
},
|
|
"volumes": [
|
|
"/services/home-assistant/config:/config"
|
|
]
|
|
}
|
|
]
|
|
}
|