BaseBuddy v0.2.0

BaseBuddy v0.2.0

BaseBuddy v0.2.0 adds the new app-data backend setup flow for self-hosted installs.

Highlights

• Choose where BaseBuddy stores its own app data during onboarding.
• Use the default basebuddy-data/ folder for simple single-server installs.
• Store BaseBuddy app data in the same Supabase/Postgres database as your content when you want one database to manage.
• Store BaseBuddy app data in a separate Supabase/Postgres database when you want cleaner production separation.
• Prepare DB-backed app data with pnpm basebuddy app-data:migrate and verify it with pnpm basebuddy app-data:check.
• Print the SQL with pnpm basebuddy app-data:sql when the runtime database role cannot create schemas or tables.
• Read the new app-data storage comparison guide before choosing a production backend.

App Data Tables

The DB-backed options create only BaseBuddy-owned tables:

basebuddy.app_state
basebuddy.audit_events

They do not rename, reshape, or migrate your content tables.

Required Env

BASEBUDDY_AUTH_SECRET=
BASEBUDDY_CONTENT_DATABASE_URL=

Optional DB-backed app-data modes:

BASEBUDDY_APP_STATE_BACKEND=supabase-same-project

or:

BASEBUDDY_APP_STATE_BACKEND=supabase-split-project
BASEBUDDY_APP_STATE_DATABASE_URL=

Links

• App data storage options: https://basebuddycms.com/docs/app-data-storage-options
• CLI reference: https://basebuddycms.com/docs/cli-reference
• First-run setup: https://basebuddycms.com/docs/first-run-setup
• Install guide: https://basebuddycms.com/docs/getting-started
• Support: https://basebuddycms.com/support

License

BaseBuddy is licensed under AGPL-3.0-or-later.