How to deploy Next.js app with Prisma and Postgres

[nicnocquee]

I have this demo Next.js app with App Router that uses Prisma to connect to a Postgres database. I have installed and deployed a Postgres DB in my server via coolify and it can be accessed from the internet.
But I cannot get the build to succeed in coolify. It just showed me incomplete error:

#13 [stage-0 9/11] RUN --mount=type=cache,id=oc080o8-next/cache,target=/app/.next/cache --mount=type=cache,id=oc080o8-node_modules/cache,target=/app/node_modules/.cache npm run build 
#13 0.684 npm WARN config production Use `--omit=dev` instead. 
#13 0.758  
#13 0.758 > [email protected] build 
#13 0.758 > npm run db:migrate && npm run db:generate && cross-env IS_BUILDING=true next build 
#13 0.758  
#13 1.132 npm WARN config production Use `--omit=dev` instead. 
#13 1.200  
#13 1.200 > [email protected] db:migrate #13 1.200 > prisma migrate deploy 
#13 1.200  #13 2.183 Environment variables loaded from .env 
#13 2.185 Prisma schema loaded from prisma/schema.prisma 
#13 2.192 Datasource "db": PostgreSQL database "databasename", schema "public" at "dbhost:dbport" 
#13 2.221  
#13 2.223 Error: Schema engine error: 
#13 2.223  
#13 ERROR: process "/bin/bash -ol pipefail -c npm run build" did not complete successfully: exit code: 1

As you can see, it only says "#13 2.223 Error: Schema engine error: ".

Meanwhile, it can be deployed successfully in Vercel.

Anybody can help?

[nicnocquee]

Turned out I couldn't use Nixpacks. Needed to use Dockerfile.

[sisou]

Did you have to write a Dockerfile yourself?

[H-Hp]

The error you're encountering seems to be related to the Prisma migration process during the build step on your Coolify server. It appears that the Prisma schema is failing to apply the required migrations to your PostgreSQL database.

Here are a few steps you can try to troubleshoot and resolve the issue:

1. Check the Prisma schema and database connection:

   • Ensure that your Prisma schema (prisma/schema.prisma) is correct and matches the structure of your PostgreSQL database.
   • Double-check your database connection URL and credentials in the Prisma schema's datasource block.
   • Try connecting to your PostgreSQL database directly (e.g., using a client like psql) to ensure that the connection works as expected.

2. Review the migration history:

   • Run npx prisma migrate status to check the migration history and see if there are any pending migrations.
   • If there are pending migrations, try running npx prisma migrate deploy locally to apply the migrations and see if any errors occur.

3. Check the Prisma logs:

   • In your Next.js app, set the LOG environment variable to DEBUG (e.g., LOG=DEBUG for Linux/macOS or set LOG=DEBUG for Windows).
   • Try running the build command (npm run build) locally and check the logs for any additional information or error messages.

4. Reset the database and migrations:

   • If the above steps don't work, you can try resetting your database and migrations by running npx prisma migrate reset.
   • This will reset your database to its initial state, allowing you to start fresh with your migrations.

5. Use a different database provider or consider other options:

   • If the issue persists, you could try using a different database provider (e.g., MySQL, SQLite) for your development and deployment environments to see if the problem is specific to PostgreSQL.
   • Alternatively, you could consider using a different ORM or database client library instead of Prisma.

6. Seek further assistance:

   • If you're still unable to resolve the issue, you can reach out to the Coolify support team or the Prisma community for further assistance.
   • Provide them with the relevant logs, your Prisma schema, and any other information that might help diagnose the problem.

It's possible that the issue is specific to the Coolify deployment environment or the way Prisma is configured in your Next.js app. By investigating the migration process and database connection, you may be able to identify and resolve the underlying cause of the error.

[osewemwai]

This is correct. You can also add a postinstall so as to generate

"scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint",
    "seed": "dotenv -e .env -- ts-node --compiler-options '{\"module\":\"CommonJS\"}' prisma/seed.ts",
    "postinstall": "prisma generate"
  },

[flawnn]

Stop posting LLM-generated content.