Prisma ORM: PostgreSQL Migrations from Dev to Production

steps

1. Modify your schema.prisma file: Define your data model changes. For example:

   Copy

   model User {
     id         Int     @id @default(autoincrement())
     name       String
     email      String  @unique
     age        Int?    @default(30)
   }

2. Run the Prisma migration tool:

   bashCopy

   npx prisma migrate dev --name "add_age_column"

   This command will create and apply migrations to the local development database.

3. Verify SQL migration files:

4. Test your changes locally: Use a local PostgreSQL instance or containerized setup via Docker.

   bashCopy

   docker run --name postgres -e POSTGRES_PASSWORD=password -d -p 5432:5432 postgres

steps

1. Create a database branch in Neon: Neon lets you create branches for development or testing purposes. Branch snapshots can be populated from production data for realistic testing.

2. Use Neon branch for schema testing: Point Prisma to the Neon branch by updating the DATABASE_URL in .env.

3. Reset branches as needed: In the Neon console, reset development branches to restore their original state.

steps

1. Include migration files in your PR: Ensure the migrations folder is pushed to version control.

2. Setup Neon in CI/CD pipelines: Create preview branches to test migrations automatically. Example GitHub Actions configuration:

   yamlCopy

   jobs:
     deploy-preview:
       runs-on: ubuntu-latest
       steps:
         - name: Check out the code
           uses: actions/checkout@v2
         - name: Set up Node.js
           uses: actions/setup-node@v2
         - name: Create Neon branch
           uses: neon/action-create-branch@v1
           with:
             branch-name: preview-${{ github.head_ref }}
             project-id: ${{ secrets.NEON_PROJECT_ID }}
         - name: Run migrations
           run: npx prisma migrate deploy

3. Automate cleanup workflows: Clean up preview branches after PRs are merged to avoid unnecessary database clutter.

steps

1. Merge pull requests: This action triggers production pipelines.

2. Run migrations in production: Use prisma migrate deploy in the CI pipeline:

   bashCopy

   npx prisma migrate deploy

3. Verify deployments: Manually test key functionality after the migrations are applied.