Prototype rapidly by pushing a Drizzle TypeScript schema's current shape directly to a database with `drizzle-kit push`, skipping SQL migration file generation entirely.

Documented steps

1. Configure `drizzle.config.ts` with `dialect`, `schema` (path to schema file(s)), and `dbCredentials` (e.g. `url: "postgresql://user:password@host:port/dbname"`), or pass equivalents via CLI flags.
2. Run `npx drizzle-kit push`. It composes a JSON snapshot of your Drizzle schema, introspects the current database schema, diffs the two, and applies the resulting ALTER/CREATE statements directly.
3. Use `--verbose` to print all SQL statements before execution, `--explain` for a dry run that prints planned changes without applying them, and `--force` to auto-accept data-loss prompts non-interactively (e.g. in CI): `npx drizzle-kit push --explain --verbose --force`.
4. Scope what push manages with `tablesFilter` (glob, default `"*"`), `schemaFilter` (default `["*"]`), and `extensionsFilters` (e.g. `["postgis"]`, default `[]`) in the config — important for shared databases or extensions that create their own tables.
5. For non-standard drivers (`aws-data-api`, `pglite`, `d1-http`) explicitly set `driver` in config alongside the matching `dbCredentials` shape (e.g. `resourceArn`/`secretArn` for aws-data-api, `accountId`/`databaseId`/`token` for d1-http).
6. Multiple environments can use separate config files via `--config=<path>`, e.g. `npx drizzle-kit push --config=drizzle-dev.config.ts`.
7. Reference: https://orm.drizzle.team/docs/drizzle-kit-push https://orm.drizzle.team/docs/migrations https://orm.drizzle.team/docs/drizzle-config-file