Support

Direct help for common BaseBuddy setup, access, mapping, editing, and deployment tasks.

Support/How to run setup checks after deployment or upgrade

How to run setup checks after deployment or upgrade

Verify BaseBuddy app data, local auth, content database, and optional storage after deployments or upgrades.

Use this guide after a deployment, upgrade, host move, database password rotation, or setup change.

BaseBuddy setup checks validate the selected app-data backend, required env values, and the content database connection. They do not require setup scripts in your content schema.

Run the CLI check

From the production working directory:

shpnpm basebuddy doctor

If you only want to validate app data and skip the live database connection:

shpnpm basebuddy doctor --skip-db-check

Open browser diagnostics

Open:

texthttps://cms.example.com/onboarding?diagnostics=1

Replace the origin with your app URL.

The diagnostics view should show ready sections for app data, owner account, environment values, database connection, and any optional storage you configured.

What to check after deployment

AreaExpected result
App dataThe deployed process can read and write the selected app-data backend
OwnerAt least one local user exists
Environment valuesBASEBUDDY_AUTH_SECRET is present and sessions can be created
Database connectionBASEBUDDY_CONTENT_DATABASE_URL reaches the mapped content database
Optional storageSupabase or S3 values are complete when configured

If the default app-data file disappears after a deploy, your host is probably using ephemeral storage. Mount persistent storage or switch to Supabase/Postgres app data.

Smoke test the app

After checks pass:

  1. Sign in.
  2. Create or open a project.
  3. Save mapping.
  4. Reload the app and confirm mapping persists.
  5. Edit one mapped content field.
  6. Confirm normal save writes only dirty mapped fields.

Publish, unpublish, and archive should still be explicit actions.