jschoubben
769f0724ca
The tool runtime's own client, mesh serve, started by the mesh on the credential it sealed to the machine (novox/hq ADR 0152, design 34): invokes every tool, listens from the machine only, holds no state. Checked with module check before it was ever registered (hq issue 148).
14 lines
711 B
Docker
14 lines
711 B
Docker
# The console (novox/hq ADR 0152, design 34): the mesh's tools for whoever is on a machine, served
|
|
# over MCP on that machine's loopback.
|
|
#
|
|
# **Nothing is compiled here.** The console is the tool runtime's own client — `mesh serve` — which
|
|
# the runtime image already carries beside the runtime it runs modules with. This recipe changes the
|
|
# program the image starts and nothing else, so the console is exactly the client a person can run by
|
|
# hand, started by the mesh instead, on the credential the mesh sealed to the machine.
|
|
#
|
|
# One base, named rather than pinned: the mesh answers with the copy it holds (novox/hq issue 044).
|
|
ARG RUNTIME_BASE
|
|
|
|
FROM ${RUNTIME_BASE}
|
|
ENTRYPOINT ["node", "dist/mesh.js"]
|