FEATUREDDeployment11 min read
Deploying a Next.js Site to Vercel: Complete Guide
The four-step deploy, the DNS records that actually matter, and the three Vercel runtime limits that break real apps after the first green build.
CATEGORY · 7 ARTICLES
Deployment
Getting the result onto the internet and keeping it there: deploying a Next.js site to Vercel, the difference between build-time and runtime environment variables and why it bites, reaching Cloudflare D1 over its HTTP API when the Workers binding does not exist, and where AI tooling fits into a deployment pipeline without being handed credentials it does not need.
Articles
FEATURED
Next.js Newsletter API with Cloudflare D1: One Insert, No Guesswork
The insert that survives duplicate requests, the safeguards around the route, and the confirmation flow this site has not built.
Oct 1310 min read
AI Coding Tools for Cloudflare Workers: Check the Runtime
Choose a coding agent by the checks it can run against Wrangler configuration, generated Env types, and a local Worker build.
Oct 99 min read
Claude Code with Cloudflare Workers: Trust Wrangler
A D1 Worker fixture shows the shortest reliable loop: configuration first, generated binding types second, implementation third.
Sep 2810 min read
Cloudflare D1 with Next.js on Vercel: The HTTP API
D1 without Workers: one wrapper module, the measured transport cost, the four error codes worth handling, and why batching and bound parameters cannot both be used.
Aug 1111 min read
Vercel Environment Variables: Build Time vs Runtime
Which of your variables are frozen into the bundle, which are read per request, and why a value that works locally can be absent in production.
Aug 1112 min read
Connecting AI Tools to Your Deployment Pipeline
A real GitHub Actions setup using this site's own typecheck, lint, and build scripts, plus where an automated AI review step should not run unattended.
Jul 298 min read