Seven tool containers move to bundles the node's runtime serves, given their words (hq ADR 0192) #242

2026-10-03T13:45:35Z

mesh-admin commented

2026-10-03 13:45:35 +00:00

hq ADR 0192, design 38 WP4b: the tools-only modules baserow, confluence, gitlab, jira, letta, searxng, unifi.

Each runtime container's environment becomes its tools bundle's env, mount targets folded back into the host paths they came from (e.g. /run/config/config.json → ${dir:mesh-state}/config.json, /run/secrets/token → ${dir:state}/token). baserow and letta reach their service on the published port (http://127.0.0.1:${port:N}) rather than the container network name. The container, base images, Dockerfile and the module's own bus credential go, and the mesh-state directory where only that credential lived (confluence, gitlab, jira). Tool code unchanged: every client is built from the environment the contributor is handed.

The controller makes the named files and directories the operator account's to read and restarts the runtime when a named file changes (#236, #237); every node's runtime hands each bundle its words (mesh-tools #33 on SDK 0.1.3, verified on all four).

Checked: each module compiled as the builder does; controller catalogue checks pass against this branch. nodered and lab stay containers for WP4c (a run-once step; an env-file and two sockets).

hq ADR 0192, design 38 WP4b: the tools-only modules baserow, confluence, gitlab, jira, letta, searxng, unifi. Each runtime container's environment becomes its tools bundle's `env`, mount targets folded back into the host paths they came from (e.g. `/run/config/config.json` → `${dir:mesh-state}/config.json`, `/run/secrets/token` → `${dir:state}/token`). baserow and letta reach their service on the published port (`http://127.0.0.1:${port:N}`) rather than the container network name. The container, base images, Dockerfile and the module's own bus credential go, and the `mesh-state` directory where only that credential lived (confluence, gitlab, jira). Tool code unchanged: every client is built from the environment the contributor is handed. The controller makes the named files and directories the operator account's to read and restarts the runtime when a named file changes (#236, #237); every node's runtime hands each bundle its words (mesh-tools #33 on SDK 0.1.3, verified on all four). Checked: each module compiled as the builder does; controller catalogue checks pass against this branch. nodered and lab stay containers for WP4c (a run-once step; an env-file and two sockets).

mesh-admin added 1 commit 2026-10-03 13:45:35 +00:00

Seven tool containers move to bundles the node's runtime serves, given their words (hq ADR 0192) 19511012f8

baserow, confluence, gitlab, jira, letta, searxng and unifi: each runtime container's
environment becomes its tools bundle's env, mount targets folded back into the host paths they
came from; baserow and letta reach their service on the published port rather than a container
network name. The container, base images, Dockerfile and the module's own bus credential go,
and the state directory where only that credential lived. Tool code is unchanged: every client
is built from the environment the contributor is handed.

mesh-admin merged commit 7c800705bf into main

2026-10-03 13:45:46 +00:00

mesh-admin deleted branch feat/0192-seven-tool-containers-move

2026-10-03 13:45:46 +00:00

mesh-admin referenced this pull request

2026-10-03 13:58:24 +00:00

The seven say what the runtime loads from their tools bundle (hq ADR 0192) #243

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#242