Modules compile in the toolchain and ship on the runtime

2026-09-14 01:57:06 +02:00
parent 5ea88b149b
commit cf116a4932
6 changed files with 39 additions and 18 deletions
@@ -6,14 +6,16 @@
 # repository and a path (novox/hq ADR 0069) rather than only on a workstation that happens to have
 # the siblings.
 #
-# Named, not pinned. The mesh answers this with the copy of the runtime it holds, because a
-# fingerprint written here would name one particular copy — the one on whichever machine the person
-# typing it was using — and on any other mesh that copy has never existed (novox/hq issue 044).
-# Declared in module.json's `build.on`; there is deliberately no default, so a build nobody told
-# stops here rather than on a reference that resolves to nothing.
+# Two bases, named rather than pinned: the image this is COMPILED in, and the image it RUNS in.
+# They are different images on purpose — the first carries a compiler and the second must not, or
+# every running container would carry one it never invokes. The mesh answers both with the copies it
+# holds, because a fingerprint written here would name one particular copy and no other mesh has it
+# (novox/hq issue 044). Declared in module.json's `build.on`; deliberately no defaults, so a build
+# nobody told stops here and says which module to build first.
+ARG BUILD_BASE
 ARG RUNTIME_BASE

-FROM ${RUNTIME_BASE} AS build
+FROM ${BUILD_BASE} AS build
 # Compiled under /app/modules so `@novox/mesh-sdk` resolves upward into the base's own
 # node_modules — the module is compiled against exactly the sdk it will run against.
 WORKDIR /app/modules/postgres