Post-Deploy Validation

After deployment, do not stop at “the homepage loads”.

NuxtBase is a full-stack product, so a meaningful post-deploy check needs to touch auth, database-backed UI, and any provider you enabled.

Minimum Smoke Test

Run this sequence against the real deployed app:

open the landing page and docs
create a new account
verify the email if email verification is enabled
sign in and reach /dashboard
confirm an active organization exists
create a project
open settings and confirm profile data loads
if enabled, test billing, storage upload, AI chat, and outbound webhooks

What To Check By Area

Auth

login page loads
register flow works
auth redirects use the production domain
protected routes redirect correctly

Database-backed features

dashboard loads real data
project create and edit work
admin pages load if you granted platform_admin

Optional providers

If enabled, verify:

Stripe checkout and webhook processing
email delivery from the real sender
file upload and public file URL resolution
AI chat responses and wallet usage
analytics loading on the expected domain

Operational Checks

Right after launch, also confirm:

logs are visible
environment values loaded as expected
background or scheduled tasks are not silently failing
memory usage is acceptable under real traffic

If you are running on Coolify, pay extra attention to memory headroom. Your tested 3.5 GB baseline should be treated as part of the validation plan, not just an install-time note.

What Counts As “Ready”

A deployment is only really ready when:

the app builds
the app boots
core user flows work
the enabled providers work
the production domain is correct
you can observe failures when something goes wrong