Central admin platform — many domains behind one hub

Teams running several domains (blog, marketplace, app, external SaaS) often build a separate admin UI per domain. Quick in the short term, but within months operators re-learn the UI per page and developers re-copy the same boilerplate. This course walks through an eight-step hub where one Next.js app directly connects to multiple PostgreSQL pools (domain DBs) and handles CRUD · audit logs · backups · OAuth.

Who it's for

• Developers who want to unify side-projects into one admin hub
• People using React 19 + Next.js App Router at realistic scale
• Anyone looking to pick up audit logs · OAuth · backup automation in one place

What you can do afterwards

• Orchestrate several PostgreSQL pools from one app
• Implement CRUD pages in 30–70 lines each with a shared AdminResourceTable
• Apply the logAdminAction fire-and-forget audit pattern
• Run Kakao / Naver OAuth with an email allow-list
• Automate pg_dump backups with cron and 7-day rolling retention
• Run one-second smoke specs over dozens of pages with Playwright manifests

Steps

1. Why a central hub — the cost of N admin UIs, benefits of unifying
2. Project setup — Next 16 + TypeScript strict + shadcn/ui + Tailwind 4
3. Multiple PostgreSQL pools — env conventions · singleton pools · query helpers
4. AdminResourceTable SSOT — shared table component · iconColor map · URL-first pagination
5. OAuth providers + allow-list — Kakao · Naver · JWT cookie sessions
6. Audit log (logAdminAction) — audit_logs table · enforced reason · per-domain viewer
7. Backup automation — pg_dump + node-cron + 30-table allow-list
8. E2E manifest + deploy — auto-generated Playwright manifest + Docker standalone

Prerequisites — getting-started + Node 20 / PostgreSQL 15 / Docker. nextjs-fullstack for App Router basics.