Correct lavinmq Dockerfile's stale MESH_TOOL_MODULES comment (061 review) #28

Merged
jschoubben merged 1 commits from fix/lavinmq-dockerfile-comment into main 2026-09-20 11:42:03 +00:00
Showing only changes of commit 17243b72df - Show all commits
+6 -5
View File
@@ -33,9 +33,10 @@ RUN node /app/node_modules/typescript/bin/tsc \
FROM ${RUNTIME_BASE}
COPY --from=build /app/modules/lavinmq/dist /app/modules/lavinmq/dist
# What a tool host should load from this module: its event consumer and its tools, which are
# separate entrypoints because they are loaded by different things. The bootstrap and the
# provisioner are not listed here — the declaration names each in its container's `args`, because
# they are what this module's own containers run. One image, because they are one module and share
# a client.
# What the runtime loads from this module in serve mode: its event consumer, its tools, and its
# provisioner — all three in one process, so the provisioner's reconcile loop runs with the broker
# connected (novox/hq issues 060/061; the provisioner used to be run as a separate container `args`
# command, which meant it served no tools and, once, ran nowhere at all). The run-once bootstrap is
# NOT listed here — it is named in its own container's `args`, because it runs to completion before
# the broker starts rather than serving. One image, because they are one module and share a client.
ENV MESH_TOOL_MODULES=/app/modules/lavinmq/dist/index.js,/app/modules/lavinmq/dist/tools/index.js,/app/modules/lavinmq/dist/provisioner/index.js