Next.js & Prisma
This site is a self-hosted Next.js App Router app with a Postgres database behind Prisma.
This site is a self-hosted Next.js App Router app with a Postgres database behind Prisma. When either project ships a security patch, a breaking CLI or a new runtime, I find out on a production site that I maintain myself. Posts here cover what I checked before upgrading, errors I hit with their exact messages, and how framework conventions like middleware matchers, robots.txt and sitemaps behave in a real deployment. When a post tests a release candidate or a sandbox instead of production, it says so up front. Each post points to the official changelog or documentation that I checked my results against.
In English
2 posts, newest first
Two Critical Next.js RCEs Shipped the Same Day: What I Actually Checked Before Patching My ServerOn August 25, 2026, Next.js shipped 15.5.24 and 16.3.3 to patch two unrelated critical RCEs at once. I run this blog's CMS as a self-hosted Next 15 app behind nginx, PM2, and Cloudflare, so nobody patched it for me. Here's the exposure check I ran before touching npm install, the actual patch commands, and why "not currently exposed" still wasn't a reason to skip the upgrade.
Prisma Shipped an Agent-Native CLI With Compute GA. I Ran It Against My Blog's Own SchemaPrisma Compute went GA on August 28, 2026, quietly bundled with a Prisma 8 CLI that drops schema.prisma for a signed "contract" model and auto-syncs Claude/Cursor/Devin skill files on install. I ran it end-to-end against a schema modeled on this blog's own Post fields, found prisma@latest is still an 8.0.0-rc.12 release candidate despite the GA changelog, and mapped exactly what would break if beru.io.vn's self-hosted Next.js + Prisma CMS moved onto it.
