Production readiness
Check BaseBuddy setup, app-data backups, storage, permissions, safe editing, and operations before production use.
Before inviting editors, verify:
| Area | Ready means |
|---|---|
| App data | The selected app-data backend exists, validates, is backed up, and is not committed |
| Env secrets | Auth secret, database URL, and optional storage keys are set outside the repo |
| Auth | Local owner sign-in works |
| Content | The content database is reachable |
| Mapping | Saved mapping persists after reload |
| Editing | Save writes dirty mapped fields only |
| Publishing | Publish, unpublish, and archive remain explicit actions |
| Storage | Mapped media/files upload and render correctly |
| Permissions | Owners, admins, editors, authors, and viewers see the expected actions |
Run:
shpnpm setup:check
pnpm basebuddy doctorWith the default backend, use a host with persistent writable storage for basebuddy-data/. If the server replaces the app filesystem on every deploy, setup changes made from the UI will not survive. For immutable or multi-server hosts, use Supabase/Postgres app data.