AI Review uses PostgreSQL as its database. Schema migrations are managed with Drizzle ORM.
Configuration
Set the DATABASE_URL environment variable to your PostgreSQL connection string:
DATABASE_URL="postgresql://user:password@host:5432/ai_review"
Migration commands
Development
Staging
Production
Run migrations against the development database:Or using the script directly:./scripts/db-migrate.sh development migrate
db:push overwrites the database schema without generating a migration history. Only use it in development environments.
Run migrations against the staging database:Or using the script directly:./scripts/db-migrate.sh staging migrate
Run migrations against the production database:pnpm db:migrate:production
./scripts/db-migrate.sh production migrate
Non-development environments require you to type the environment name (production) at the confirmation prompt before the migration executes. This is a safety guard against accidental runs.
- Run the migration before deploying the new application version
- Confirm a valid backup exists before running
- Use a minimal-privilege database account for the application process
- Validate the migration on staging first
Drizzle Studio
Open the Drizzle Studio GUI to inspect and manage the database:
pnpm --filter server db:studio
DATABASE_URL.
Generating migrations
When you modify the Drizzle schema files, generate a new migration:
pnpm --filter server db:generate
Development data directory
The development Docker Compose configuration stores PostgreSQL data in:
The full development data layout is:
./data/
├── logs/
├── postgres/
├── redis/
└── gitlab/
Resetting the development environment
pnpm env:reset is a destructive operation. It deletes all local development containers, volumes, and the contents of ./data. This cannot be undone.
pnpm env:init to restore the development environment and re-run migrations.