pb-migrations

Topics in the source

• PocketBase Migrations & Schema Versioning
• Overview
• CLI Commands
• Auto-migrate Mode
• Migration File Format
• Creating Collections Programmatically
• Base collection
• Auth collection

PocketBase supports two approaches to schema management: 1. Auto-migrate (default in dev) — Dashboard changes auto-generate migration files in pbmigrations/ 2. Manual migrations — write migration files by hand for full control Enabled by default. When you change collections in the Dashboard, PocketBase auto-generates migration files in pbmigrations/. Workflow: 1. Develop with auto-migrate ON — use Dashboard to design schema 2. Migration files are auto-generated in pbmigrations/ 3. Commit these files to git 4. Deploy: migrations run automatically on serve start 5. In production: use --automigrate=0 to prevent Dashboard changes from generating new migrations Important: the app inside migrations is a transactional instance. If any error occurs, the entire migration is rolled back. Warning: raw SQL bypasses PocketBase's schema cache. Run migrate collections afterward to re-sync if needed. ./pocketbase migrate collections generates a complete snapshot — useful for: Bootstrapping a new environment Resetting migration history Reviewing full schema in one file The generated file uses app.importCollections(collections) which supports two modes: Default (merge/extend): adds new collections a

This is an excerpt. Refer to the complete source and its current requirements.