Build dashboard assets in runtime image
Some checks failed
deploy / deploy (push) Has been cancelled

Proof: Include the multistage Dockerfile needed to build operator-dashboard static assets and copy them into the production image so the deployed dashboard backend can serve the new UI.

Assumptions: The dashboard frontend should be built during image creation rather than committed as generated dist artifacts.

Still fake: External alert receiver remains unconfigured; this commit only resolves the live dashboard asset packaging blocker.
This commit is contained in:
philipp 2026-04-08 19:39:44 +02:00
parent 3fd0d8fe46
commit 3226a68613

View file

@ -1,3 +1,12 @@
FROM node:22-bookworm-slim AS dashboard-builder
WORKDIR /app
COPY package.json package-lock.json ./
RUN npm ci
COPY . .
RUN npm run operator-dashboard:build
FROM node:22-bookworm-slim
WORKDIR /app
@ -5,6 +14,7 @@ COPY package.json package-lock.json ./
RUN npm ci --omit=dev
COPY . .
COPY --from=dashboard-builder /app/src/operator-dashboard/dist ./src/operator-dashboard/dist
ENV NODE_ENV=production
CMD ["node", "src/apps/near-intents-ingest.mjs"]