The catalogue builds its own runtime, and postgres serves its tools

Both modules keep their tools in an entrypoint of their own, so an image that named only the consumer would serve none of them.
2026-09-13 01:13:43 +02:00
parent d6c9c8d666
commit e742b6a569
3 changed files with 48 additions and 5 deletions
@@ -23,6 +23,8 @@ RUN node /app/node_modules/typescript/bin/tsc client.ts index.ts provisioner/ind

 FROM ${RUNTIME_BASE}
 COPY --from=build /app/modules/postgres/dist /app/modules/postgres/dist
-# Which of the three the container runs is the declaration's business, said in its `args` — one
-# image, because they are one module and share a client.
-ENV MESH_TOOL_MODULES=/app/modules/postgres/dist/index.js
+# 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 provisioner is the third,
+# and is not listed here — the declaration names it in the container's `args`, because it is what
+# this module's own container runs. One image, because they are one module and share a client.
+ENV MESH_TOOL_MODULES=/app/modules/postgres/dist/index.js,/app/modules/postgres/dist/tools/index.js