jochen 6a6d5747a3 nodered: the runtime serves its tools, and its mqtt step is a run-once process (hq ADR 0198) ...

The mesh-nodered container goes with its Dockerfile, build bases and bus credential. The mqtt step runs node on the bundle and reads the binding and settings files where the mesh writes them, from an env-file the mesh fills because a process's env is not given ${port:…}.

2026-10-03 23:33:51 +02:00

..

mqtt

nodered: its MQTT broker comes from the mesh

2026-09-30 13:01:14 +02:00

test

nodered: its MQTT broker comes from the mesh

2026-09-30 13:01:14 +02:00

tools

Event names are local now, in the manifests and in the code

2026-09-27 14:42:28 +02:00

client.ts

nodered: its MQTT broker comes from the mesh

2026-09-30 13:01:14 +02:00

module.json

nodered: the runtime serves its tools, and its mqtt step is a run-once process (hq ADR 0198)

2026-10-03 23:33:51 +02:00

package.json

nodered: its MQTT broker comes from the mesh

2026-09-30 13:01:14 +02:00

tsconfig.json

nodered: its MQTT broker comes from the mesh

2026-09-30 13:01:14 +02:00