Dev→prod schema workflow (push-only, no migrations dir)

Generated from mcp/patterns.registry.json — do not edit by hand; change the registry and run bun run patterns:build.

Index card — the docs below are the canonical explanation; deep-tier pattern pages additionally carry invariants and emulation notes.

Category: Database Operations · Tier: light · Risk: low — dev-time workflow/config, no runtime dependency

Uses drizzle-kit push for schema changes during development and defers versioned generate/migrate SQL files until production holds real data.

When to use: Follow this while prototyping solo, then switch to generate+migrate before a production database with real user data goes live.

Docs

• docs/blueprint/data/drizzle-workflow.md (GitHub · GitLab)

Code

• drizzle.config.ts (GitHub · GitLab)

Machine-readable record: db-ops-dev-prod-schema-workflow in mcp/patterns.registry.json.