Skip to main content
Letnull19A Portfolio
2026-08-31//4 MIN READ//DEVOPS // DEPLOYMENT

STATIC EXPORT DEPLOYMENT WITH DOCKER AND DOKPLOY

Root-context Docker builds, NEXT_PUBLIC env baking, and runtime fallbacks that keep the site alive without a backend.

STATIC EXPORT DEPLOYMENT WITH DOCKER AND DOKPLOY

Static Export Deployment

output: "export" turns the frontend into plain files. The question is how to serve and configure them.

Docker build

  1. Build from the monorepo root context so packages/ are visible.
  2. Compile shared packages first, then the frontend.
  3. Copy out/ and public/ into a static-web-server image.

Env vars are baked in

NEXT_PUBLIC_* values are inlined into the bundle at build time. Changing NEXT_PUBLIC_API_URL means rebuilding the image, not restarting the container.

Runtime resilience

Sections use react-query with a fallback to local mocks. The static export stays fully renderable even when the API is unreachable.

END OF SIGNALSHARE OR SAVE THIS KNOWLEDGE
LINKEDINTELEGRAM

MORE ARTICLES

UI DESIGN SYSTEM & MARKDOWN SYNTAX DEMO

Complete showcase of all typography, lists, code blocks, tables, and blockquotes supported by the markdown parser.

linkedintelegramRead here
MONOREPO INFRASTRUCTURE WITH PNPM WORKSPACES

MONOREPO INFRASTRUCTURE WITH PNPM WORKSPACES

How to split Next.js frontend and Node.js backend into a pnpm monorepo with isolated Dockerfiles.

linkedintelegramRead here

CONTRACT-FIRST API WITH T RPC AND SHARED ZOD SCHEMAS

Why the API contract lives in code: shared zod schemas, envelope-less tRPC responses, and fail-fast data validation.

linkedintelegramRead here

ASK ABOUT MY WORK.

Ask about product fit, engineering decisions, or the stack behind a specific case — personal AI got you covered.

LET'S WORK TOGETHER

A new product, an unfinished system or something that needs fixing? Tell me about your project!

YOU CAN ALSO WRITE AN EMAIL ON LETNULL19A@GMAIL.COM