Files
jschoubben 08d5c118d3 Become a nox mesh module
The mesh builds all three images from this repository and a commit
(novox/hq ADR 0069) — the Drone pipeline that built outside Docker and
copied its output in retires with the predecessor. One module carries the
API and every client instance: eef and filip are the same built client
under two names, which is a second route contribution, not a second
module (ADR 0015 — an application is one repository).

The clients drop nginx and its bash startup script: the node the API
already needs serves the static build too (client-server/serve.mjs —
files, the SPA fallback, env-config.js from the environment), so the
whole module stands on one declared base.

What the machine serves does not move: the same four public names, the
same four machine ports. MongoDB, the bucket and every credential arrive
as mesh grants instead of hand-set environment; SUPER_ADMIN_KEY stops
being a default written in code and becomes a minted secret.
2026-09-25 20:50:19 +02:00

22 lines
676 B
Docker

# The photos admin client, built by the mesh from this repository (novox/hq ADR 0069). The same
# shape as client/Dockerfile — see the notes there; only the source directory differs.
#
# The build context is the repository root; every COPY says so.
ARG NODE_BASE
FROM ${NODE_BASE} AS build
WORKDIR /build
COPY admin-client/package.json admin-client/package-lock.json ./
RUN npm ci
COPY admin-client/public ./public
COPY admin-client/src ./src
COPY admin-client/.env ./.env
RUN npm run build
FROM ${NODE_BASE}
ENV NODE_ENV=production
COPY client-server/serve.mjs /serve.mjs
COPY --from=build /build/build /site/
COPY admin-client/.env /site/.env
CMD ["node", "/serve.mjs"]