Documentation

Practical product docs for setting up, mapping, editing, and operating BaseBuddy.

Docs/Operations

Operations

Back up, upgrade, and operate a BaseBuddy install safely.

BaseBuddy app state lives in one selected app-data backend. The default is basebuddy-data/basebuddy.config.json; Supabase/Postgres app-data mode stores the same state in BaseBuddy-owned basebuddy tables. Back up the selected backend before upgrades, credential rotation, and host migrations. Env secrets and content database backups are separate.

Backup Checklist

  • BaseBuddy app data: basebuddy-data/basebuddy.config.json or the basebuddy schema tables
  • content database backups
  • storage provider buckets, if you use mapped media/files
  • deployment env values for public branding and docs links
  • deployment env secrets for auth signing, database access, and optional storage

Upgrade Checklist

  1. Back up BaseBuddy app data.
  2. Back up the content database.
  3. Deploy the new code.
  4. Run pnpm setup:check.
  5. Run pnpm basebuddy doctor.
  6. Verify sign-in, project list, mapping persistence, and one safe content edit.

Rollback

Restore the previous code and matching app-data backup together. Restore the content database only if content data itself changed and needs rollback.

Hosting Note

With the default backend, editable installs need persistent writable storage for basebuddy-data/basebuddy.config.json and basebuddy-data/basebuddy.audit.jsonl. For immutable hosts or multi-server deploys, use Supabase/Postgres app data.