Check a Replit Agent Full-Stack App Before Publishing

The Replit workspace preview and a published site can have different commands and environment settings. A full-stack app is ready for people to use when the public build starts, reaches its database, and applies the same rules the preview passed.

Worked example

Staging acceptance checklist for a meeting room app

Open the home page → page loads
Sign in as fixture account → room list visible
Create booking STAGE-014 → list shows new booking
Refresh after republish → booking remains
Open booking as an unrelated test account → access denied

Steps

  1. Confirm the publishing settings have the intended start command and server deployment type. For a web app with variable traffic, inspect Autoscale settings and estimated charges before publishing a staging copy.
  2. Use separate test secrets and a staging database. With the sample acceptance cases, record the expected response for a basic page, a read, a write, and an unauthorized action.
  3. Run each case against the published staging address. Restart or republish the staging app, then check whether the synthetic record is still available to the assigned test account.

What to check

  • If the workspace passes and the published site fails, inspect publishing logs, secrets, and database configuration before changing app code.
  • Use a durable store for records that must survive restarts. Check billing and resource limits for the selected deployment before inviting real users.

See the Replit tool profile

References