How to back up before upgrades
Back up BaseBuddy app data and the content database before changing versions, credentials, or deployment storage.
Use this before upgrading BaseBuddy, rotating database credentials, moving hosts, or changing where the app stores setup state.
BaseBuddy setup state lives in one selected app-data backend. The default backend is:
textbasebuddy-data/basebuddy.config.jsonSupabase/Postgres app-data installs store the same state in BaseBuddy-owned basebuddy schema tables.
Back up BaseBuddy app data
For the default backend, make a private backup of basebuddy-data/basebuddy.config.json from the production working directory. For Supabase/Postgres app data, back up the basebuddy schema tables. Keep the backup secret because it contains local user records, password hashes, session hashes, projects, permissions, invitations, mappings, and sidebar layout.
Database URLs, storage keys, and signing secrets are not stored in app data; back those up separately through your deployment secret manager.
Do not upload the backup to public issue trackers, public object storage, or screenshots.
Back up the content database
Back up the Postgres database that stores your content tables using your normal database provider workflow. In Supabase, use a snapshot, PITR, or SQL dump depending on your plan and recovery needs.
BaseBuddy does not reshape your content schema during setup, but mapped edits still write to your content tables. A database backup is the rollback point for content changes.
Verify both backups
Before upgrading:
- Confirm the app-data backup exists and is readable.
- Confirm the database backup or restore point finished.
- Record the BaseBuddy version or commit you are running now.
- Record where production stores BaseBuddy app data.
After upgrading, run:
shpnpm basebuddy doctorThen sign in and confirm projects, mappings, and member settings still appear.