Deployment

Deployment is where the template stops being a local starter and becomes a real service.

NuxtBase is not just a static marketing app. The template codebase depends on:

server API routes
PostgreSQL
Better Auth callbacks
background and scheduled Nitro tasks
optional external providers such as Stripe, storage, email, and AI

So production deployment should be treated like a full-stack application rollout.

Reading Order

Production Checklist Validate runtime, secrets, resources, and provider readiness before launch.

Domain & DNS Align your public site URL, auth URL, and callback origins with the real production domain.

Post-Deploy Validation Run a practical smoke test after the app is live.

What This Section Covers

production runtime assumptions
provider and secret readiness
domain and callback alignment
final user-flow validation after deploy

Pre-Launch Checklist

confirm all required environment variables exist
verify database connectivity in the target environment
confirm auth and billing callbacks use production URLs
test the main user journey before you announce anything

Keep It Boring

The safest deployment plan is the smallest one that proves the system works. Avoid combining infrastructure changes, pricing changes, and auth changes in a single release when you can stage them.