AEAl-Andalus⺢Experience
Sign in · Join
AEAl-Andalus⺢Experience
ProjectsGalleryAboutArticlesDashboardAPI
© 2026 — Modular content systems☕buy me a coffee
Framework Study Guide
ChaptersCardsLegendRoadmapRoute Map
Chapters
00 · Root Layout01 · Server Page (page.tsx)01a · Special Files (not-found, error, loading)02 · Client Component (UI & Interaction)02a · Client Boundaries & Islands03 · Entity Actions (actions/*.ts)04 · Server Actions ("use server")05 · Context Provider (context/*.tsx)06 · API Route (app/(api)/<entity>/route.ts)07 · TypeScript + Prisma08 · Entity-First Feature Design09 · Deployment, Docker & Cloud10 · Next 16 + Prisma 7 Upgrade11 · Prisma 7 (SQLite-first, App Router)12 · TypeORM (Entities + Migrations)13 · Drizzle ORM (SQL-first)11 · CSS, Mobile-First Flex, Tailwind12 · Libraries, Accelerators & Production Shortcuts14 · Next.js 16: cache, PPR, proxy, AI
→ cards/09-deployment

Chapter

09 · Deployment, Docker & Cloud

Treat deployment as a contract: build, run, migrate, seed; keep steps explicit.

Mental Model

  • Build artifacts are immutable; config/env are runtime inputs.
  • Migrations are explicit; seeds are intentional (dev/test only).

Checklist

# build
npm run build

# prisma
npx prisma migrate deploy
npx prisma db seed

# docker (example)
docker build -t app .
docker run -p 3000:3000 --env-file .env app

Rules of Thumb

  • No implicit migrations on startup; run them explicitly.
  • Config/env are ⚫; never bake secrets into images.
  • Health/readiness checks are UX for ops; keep them simple.