Capstone: A Complete, Working Flexible-Routing Site

Sam opens the site. Apache's own mod_proxy_http forwards the request to the standalone Node server, kept alive under PM2's own supervision on the same already-live Apache the site has always run behind.

Sam enters the legacy admin credential. @auth/astro's own Credentials provider runs its authorize() callback, and bcryptjs — the identical package the Next.js rebuild already used — verifies it against the stored $2y$-tagged hash with no configuration needed.

Through the hand-built admin interface — no free admin, no scaffold generator, the most minimal starting point of all five siblings — Sam creates programming, then general-purpose-languages, then java, then fundamentals, then chapter-1. Each save calls Chapter 2's own explicit computeFullPath helper, since Drizzle has no lifecycle hooks to do it automatically.

Visiting the full five-segment path, Chapter 3's [...path].astro resolves it with a single Drizzle query — no getStaticPaths() anywhere — and Chapter 4's PageLayout renders the breadcrumb and set:html={page.body} content, styled by Chapter 5's dark theme.

Sam edits the Chapter 1 page's title. Chapter 8's endpoint and Zod validation handle the submission exactly as before — but Chapter 9's getSession(request) check is now in place, the first genuine "place for an auth check" this course ever had. Logged out, the identical request now returns a 401 instead.

Sam decides fundamentals belongs under a different parent. Chapter 10's movePage updates fundamentals' own fullPath first, then updateDescendantPaths recurses down and updates chapter-1's path too — the real payment of the cascade cost Chapter 2 deliberately deferred at the very start of the course.

Sam tries to delete java, which still has fundamentals beneath it. Chapter 2's onDelete: 'restrict' database constraint refuses the operation, and Chapter 10's try/catch turns the raw database exception into a real, readable 409 response — the same ceremony Laravel's own capstone needed, not Rails' smoother built-in path.

Sam visits the kanji page. Chapter 7's resolution holds on both fronts: the routing and rendering were already solved by Chapters 2 and 4, and JavaScript's own UTF-16 string model — the same one Next.js already relied on — never risked corrupting the character. The database's own utf8mb4 charset, set explicitly on the mysql2 connection since no automatic default existed here, stores it correctly.

Sam checks the query log while loading the breadcrumb-heavy Chapter 1 page. Chapter 6's db.query.pages.findFirst({ with: ... }) is doing its job — the same deliberately-planted N+1 pattern caught a fifth time, resolved via Drizzle's own relational API, verified as genuinely mirroring Prisma's own include.

Sam confirms PM2 shows the Node process running cleanly, and that Apache's own mod_proxy_http is forwarding requests correctly — the last confirmation in a series that has now rebuilt the same real site five separate times.