A Five-Rule Checklist for Deploying Next.js on a VPS in Production

·12 views

A guide on deploying Next.js apps to a VPS argues that basic tutorials omit practical rules needed for production stability. It recommends installing Node 22 LTS from NodeSource rather than the outdated default Ubuntu package, and using npm ci so the server matches the lockfile. The author stresses confirming a finished build, since restarting during a build can leave a half-written directory serving stale content. The piece also warns that NEXT_PUBLIC_ variables are baked in at build time and require a rebuild, while builds can be silently killed by memory limits on 1 GB servers. Finally, it advises using PM2 as a process manager and running the build before restarting the app.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Walk&Relax: Open-Source Web App Combines Nature Sounds, Step Counting and Sleep Timer

Walk&Relax is an open-source web application that merges relaxation audio, walking tracking and bedtime tools into one free platform. It generates nature sounds such as rain, wind, birdsong and crickets entirely offline using Web Audio synthesis, avoiding downloads and subscriptions. The app uses a phone's motion sensors to count steps and estimate calories burned, with an indoor pace mode also available. It further offers a sleep timer that fades audio gradually, along with a dimmable OLED bedside clock and a guided breathing exercise. The project was developed as a submission to the Hacktoberfest Open-Source AI Challenge and can be deployed on Render.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Routing AI Agent Models by Step Cut Latency 86%, After Fixing Root Causes of a $48,000 Error

A follow-up post from a billing-agent team describes how it addressed upstream causes of an incident in which its agent settled a $48,000 credit that should have gone to a human. The team tested whether dumping a 350-page finance handbook into a long-context prompt could replace its retrieval pipeline, finding the cost gap real but modest and raising concerns about recall and traceability. The root cause traced to a naive chunking script that split a formula from the condition that made it inapplicable, so the agent saw the formula without its precondition. The team responded with section-aware parent-child chunking that returns full sections and version-stamps documents. The post also covers why a six-step ticket took 42.6 seconds and cost $0.184, and the latency gains from routing models by step.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Deploys Break Open Browser Tabs via ChunkLoadError from Deployment Skew

A developer found that a routine deploy triggered a spike in ChunkLoadError reports unrelated to any code change in the diff. The errors came from browser sessions that had loaded the page before the deploy finished, since their open tabs still referenced content-hashed filenames that the new build replaced. This mismatch between an older client and a newer server is known as deployment skew, and it can affect static chunks, RSC payloads, Server Action IDs, and API request shapes. Suggested mitigations include Next.js's deploymentId option, Vercel Skew Protection, and a one-time client-side reload guarded against loops.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

WebMCP Proposal Lets Websites Expose Callable Actions to AI Agents

WebMCP is a proposed standard that lets a webpage declare the actions it supports, along with JSON Schema definitions, so AI agents can call them directly instead of reading and clicking through the interface. Chrome announced an early preview in February 2026, and the specification is being developed at the W3C with Microsoft's involvement. Unlike server-side MCP, WebMCP tools run in the user's browser tab under the user's existing session, which avoids building a separate authentication system but introduces its own security considerations. The API is still experimental and its method names have changed between Chrome versions, so developers are advised to check current documentation before relying on it. The author suggests prototyping with WebMCP is worthwhile now, while committing a production launch to it is premature.

0 comments Read more at DEV Community