Document blog production build and prune old posts

Author: AnastaZIuk

Caddyfile

@@ -0,0 +1,8 @@
+:3000 {
+    @root path /
+    redir @root /blog/ 308
+    handle_path /blog* {
+        root * /srv/blog
+        file_server
+    }
+}

Dockerfile

@@ -0,0 +1,30 @@
+# syntax=docker/dockerfile:1
+
+FROM node:20-alpine AS build
+WORKDIR /app
+
+ENV NODE_ENV=production \
+    NEXT_TELEMETRY_DISABLED=1
+
+RUN apk add --no-cache libc6-compat
+
+COPY package.json package-lock.json ./
+RUN npm ci
+
+COPY . .
+
+ARG BLOG_BASEURL=/
+ENV BLOG_BASEURL=${BLOG_BASEURL}
+
+RUN npm run build
+
+FROM caddy:2.9-alpine AS runner
+WORKDIR /srv/blog
+
+RUN addgroup -S caddy && adduser -S caddy -G caddy
+COPY --from=build --chown=caddy:caddy /app/build ./
+COPY Caddyfile /etc/caddy/Caddyfile
+
+EXPOSE 3000
+USER caddy
+ENTRYPOINT ["caddy", "run", "--config", "/etc/caddy/Caddyfile"]

README.md

@@ -58,3 +58,8 @@ The Graphics Programming Blog - A collection of technical articles, project post
   ```
 
 - `http://localhost:3000` should open automatically
+
+## Production image
+- Build: `npm run build` produces the `build/` directory.
+- Final container copies only `build/` plus the Caddy service binary; there is no Node/npm runtime remaining, everything is pre-rendered.
+- Run in production with `--read-only` and `tmpfs` (e.g. `/tmp:size=32m`, `/config:size=32m`, `/data:size=32m`) so Caddy can keep its cache/autosave files while leaving the image immutable.