Getting ready to publish
What "environments" mean here, and a checklist before you go live.
There are no separate environments #
If you're used to dev / staging / production copies, set that expectation aside. A Vibe app has two states of the same project, not separate environments:
| State | Where | What it is |
|---|---|---|
| Preview | dev-<slug>.tada.app | Your live editing surface — hot-reloads as you and the agent work. |
| Published | <slug>.tada.app | The last release you published, serving your end users. |
Preview touches real data #
Because both states point at the same Tadabase backend, actions you take in preview — creating a record, triggering a workflow, sending an email — hit your real data and real integrations. While you're still shaping an app, prefer reading data and test records over firing production workflows.
Pre-publish checklist #
- RLS is on and tested Sign in as a real end-user of each role and confirm they see exactly what they should. This is the single most important check.
- Secrets are set Any API key your routes read from process.env is added under Settings → Secrets — not left in a file.
- The build is clean No unresolved errors in the Errors tab; the preview renders the flows your users will hit.
- Auth flow works Sign-in, sign-up (if enabled), and password reset all complete against your Tadabase users.
- Review the Changes tab Confirm the files moving into this release are the ones you expect.