vercel

Pushes to our staging branch kept creating throwaway preview deploys. One git.deploymentEnabled block in vercel.json ended it.

TL;DR: Vercel deploys every pushed branch by default, so a repo with main and stag ends up with redundant preview deployments. An eight-line vercel.json using git.deploymentEnabled silences stag while keeping main on production. It beats the Ignored Build Step because declarative JSON can't invert exit codes or rot, just avoid overlapping glob rules.

The diff was docs-only, yet the deploy migration from Cloudflare Workers to Vercel still happened. The wiring lives in the Vercel dashboard and GitHub settings, not in the repo.

TL;DR: A docs-only commit revealed the Workers-to-Vercel migration left almost no trace in Git, since the wiring lives in Vercel and GitHub settings. Vercel elects the production branch only at import, so the GitHub default branch stag and production branch main are two independent switches. Env variables need per-target re-registration, and rollback is repointing a deployment, not git revert.

Vercel infers the package manager from the lockfile, not package.json. One leftover pnpm-lock.yaml failed the deploy with ERR_PNPM_OUTDATED_LOCKFILE.

How I split a Next.js sitemap into 200-URL child files, listed them in robots.txt, and what Google actually reads from a sitemap.

How I split a Next.js sitemap into 200-URL child files with generateSitemaps, listed them in robots.txt, and what Google actually reads from a sitemap.

Vercel's iad1 Washington default only affects functions — the 126-PoP CDN already serves readers from Singapore. How to pick and switch the right region.

A three-lane branch model for safe deploys: main as the source of truth, staging for Vercel previews, api for VPS deploys via GitHub Actions.

Notes from moving this blog's frontend to Vercel: Next.js standalone output, a multi-stage Dockerfile for a lean image, and preview deployments per branch.