Repository navigation
Expand file tree
/
Copy pathDockerfile
More file actions
214 lines (164 loc) · 9.35 KB
/
Copy pathDockerfile
File metadata and controls
214 lines (164 loc) · 9.35 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
# ============================================================
# Stage 1: package-prep — strip version from root package.json
# ============================================================
# Separate stage so that COPY --from uses content-based caching.
# Even if this stage rebuilds on version bump, the OUTPUT is
# identical (version removed), so downstream COPY --from hits cache.
# Pinned deno version — matches docker-compose deno runtime (denoland/deno:alpine-2.0.6)
ARG DENO_VERSION=2.0.6
FROM denoland/deno:alpine-${DENO_VERSION} AS deno-bin
FROM node:20-alpine AS package-prep
RUN apk add --no-cache jq
COPY package.json /tmp/package.json
RUN mkdir -p /out && \
jq 'del(.version) | .workspaces = [.workspaces[] | select(. != "mcp")]' \
/tmp/package.json > /out/package.json
# ============================================================
# Stage 2: deps — ALL dependencies (dev + prod) for building
# ============================================================
FROM node:20-alpine AS deps
WORKDIR /app
# Root package.json comes from package-prep (version stripped).
# COPY --from uses content-based cache: if output is identical,
# this layer and npm install below stay cached across releases.
COPY --from=package-prep /out/package.json ./package.json
COPY package-lock.json ./package-lock.json
COPY backend/package.json ./backend/package.json
COPY frontend/package.json ./frontend/package.json
COPY packages/dashboard/package.json ./packages/dashboard/package.json
COPY packages/shared-schemas/package.json ./packages/shared-schemas/package.json
COPY packages/ui/package.json ./packages/ui/package.json
# Strip prepare/build scripts from shared-schemas to prevent tsc
# from running during install (source files aren't copied yet).
# The actual build happens in the build stage with full source.
RUN apk add --no-cache jq && \
jq 'del(.scripts.prepare, .scripts.build)' \
packages/shared-schemas/package.json > packages/shared-schemas/package.json.tmp && \
mv packages/shared-schemas/package.json.tmp packages/shared-schemas/package.json
RUN npm ci && npm cache clean --force
# ============================================================
# Stage 3: build — compile all packages
# ============================================================
FROM deps AS build
COPY . .
# Vite bakes these into static bundles at compile time
ARG VITE_API_BASE_URL
ARG VITE_PUBLIC_POSTHOG_KEY
# Build order: shared packages → backend → frontend
RUN npm run build
# ============================================================
# Stage 4: prod-deps — production dependencies only
# ============================================================
FROM node:20-alpine AS prod-deps
WORKDIR /app
COPY --from=package-prep /out/package.json ./package.json
COPY package-lock.json ./package-lock.json
COPY backend/package.json ./backend/package.json
COPY frontend/package.json ./frontend/package.json
COPY packages/dashboard/package.json ./packages/dashboard/package.json
COPY packages/shared-schemas/package.json ./packages/shared-schemas/package.json
COPY packages/ui/package.json ./packages/ui/package.json
# Strip prepare/build scripts from shared-schemas to prevent tsc
# from running during install (tsc is a devDependency, not available here).
# The compiled output comes from the build stage instead.
RUN apk add --no-cache jq && \
jq 'del(.scripts.prepare, .scripts.build)' \
packages/shared-schemas/package.json > packages/shared-schemas/package.json.tmp && \
mv packages/shared-schemas/package.json.tmp packages/shared-schemas/package.json
RUN npm ci --omit=dev && npm cache clean --force
# ============================================================
# Stage 5: runner — minimal production image
# ============================================================
FROM node:20-alpine AS runner
# tini: proper PID 1 for signal forwarding and zombie reaping
# postgresql16-client: pg_dump/pg_restore for database backups. Keep the
# client major at 16 while the bundled postgres image is on 15 — pg_dump 17+
# emits settings (e.g. transaction_timeout) that a 15 server rejects, which
# would make every restore fail.
# su-exec: the entrypoint drops root to `node` after joining the Docker socket's
# group. `su` would leave a shell between tini and node, breaking signal delivery.
RUN apk add --no-cache tini postgresql16-client su-exec
WORKDIR /app
# Run as non-root using the built-in node user (uid 1000)
# /data: database dir (matches DatabaseManager default)
# Default STORAGE_DIR and LOGS_DIR so every containerised deployment
# (docker run, Compose, Zeabur, Render, etc.) writes to the well-known
# mount points. Compose and PaaS env vars override these when set.
ENV STORAGE_DIR=/insforge-storage
ENV LOGS_DIR=/insforge-logs
ENV MAX_JSON_BODY_SIZE=100mb
ENV MAX_URLENCODED_BODY_SIZE=10mb
# Express production mode + telemetry runtime_environment classification.
# Only safe in this stage: node_modules are copied in prebuilt, so no npm
# install runs under it. Do NOT set this in the dev stage — its containers
# run `npm install` at startup, which would skip devDependencies.
ENV NODE_ENV=production
# Telemetry deployment-channel default for bare `docker run`. Compose files
# and PaaS templates override it; platform-injected vars win over both.
ENV INSFORGE_DEPLOYMENT_METHOD=docker
RUN mkdir -p /data /insforge-storage /insforge-logs && \
chown node:node /data /insforge-storage /insforge-logs
# tsx is a devDependency but required at runtime for migrate:bootstrap
RUN npm install -g "tsx@^4.7.1" && npm cache clean --force
# --- Stable layers first (change only when dependencies change) ---
# Production node_modules (hoisted by npm workspaces)
COPY --from=prod-deps --chown=node:node /app/node_modules ./node_modules
# --- Volatile layers last (change every release) ---
# Compiled output: server.js + frontend/ static files
COPY --from=build --chown=node:node /app/dist ./dist
# Runtime docs for /api/docs endpoints and documentation assets
COPY --from=build --chown=node:node /app/docs ./docs
COPY --from=build --chown=node:node /app/.agents/docs ./.agents/docs
# Migration runtime: tsx resolves @/* aliases via tsconfig.json,
# node-pg-migrate reads .sql files from backend/src/
COPY --from=build --chown=node:node /app/backend/src ./backend/src
COPY --from=build --chown=node:node /app/backend/tsconfig.json ./backend/tsconfig.json
# Workspace packages needed at runtime:
# - shared-schemas: backend bootstrap/migrations resolve source via tsconfig paths
# - package.json + dist keep workspace links in node_modules valid
COPY --from=build --chown=node:node /app/packages/shared-schemas/package.json ./packages/shared-schemas/package.json
COPY --from=build --chown=node:node /app/packages/shared-schemas/dist ./packages/shared-schemas/dist
COPY --from=build --chown=node:node /app/packages/shared-schemas/src ./packages/shared-schemas/src
# Package manifests for npm scripts
COPY --from=build --chown=node:node /app/backend/package.json ./backend/package.json
COPY --from=build --chown=node:node /app/package.json ./package.json
# Deliberately still root at this point. The entrypoint reads the group off a mounted
# Docker socket — a host-specific id that cannot be baked in and should not have to be
# supplied — then execs the command as `node`. Nothing in the app runs as root.
#
# The trade this makes, stated plainly: without `USER node` the image no longer enforces
# non-root by itself, so `--entrypoint` (or a compose `entrypoint:` override) bypasses
# the handoff and runs as root. The drop is in the entrypoint, not the image metadata.
# This is the same shape the official postgres and redis images use for the same reason;
# if you override the entrypoint, add `user: node` yourself.
COPY --chmod=755 docker/entrypoint.sh /usr/local/bin/insforge-entrypoint
EXPOSE 7130 7131
ENTRYPOINT ["/sbin/tini", "--", "/usr/local/bin/insforge-entrypoint"]
# Exec node directly instead of `npm start`: the npm wrapper chain
# (npm start -> npm run start -> node) keeps two extra npm processes resident
# (~20-40MB on a 512MB nano) and breaks direct signal delivery. cwd stays
# /app/backend, matching what `npm run start` ("node ../dist/server.js") used.
CMD ["sh", "-c", "cd backend && npm run migrate:up && exec node ../dist/server.js"]
# ============================================================
# Stage: dev — development image (used by docker-compose)
# ============================================================
# Source code is mounted via volumes, only needs Node.js + Deno.
FROM node:20-alpine AS dev
COPY --from=deno-bin /bin/deno /usr/local/bin/deno
# pg_dump/pg_restore for database backups (see runner stage for the
# version-pinning rationale)
RUN apk add --no-cache postgresql16-client
WORKDIR /app
# Default mount points (same as runner stage — see comments there)
ENV STORAGE_DIR=/insforge-storage
ENV LOGS_DIR=/insforge-logs
ENV MAX_JSON_BODY_SIZE=100mb
ENV MAX_URLENCODED_BODY_SIZE=10mb
# Pre-create volume mount points so Docker initializes named volumes
# with these directories instead of creating them as root-owned.
# No USER node here: dev containers use bind mounts for source code,
# which inherit host user ownership. Running as node would break
# npm install on root-owned bind mounts (e.g. in CI).
RUN mkdir -p /app/node_modules /app/backend/node_modules /app/frontend/node_modules \
/app/shared-schemas/node_modules /app/ui/node_modules \
/insforge-storage /insforge-logs