fix(api): add debian-openssl-3.0.x to Prisma binaryTargets
All checks were successful
ci/woodpecker/push/api Pipeline was successful
All checks were successful
ci/woodpecker/push/api Pipeline was successful
Prisma client was generated for debian-openssl-1.1.x but the node:24-slim Docker image runs Debian Bookworm with OpenSSL 3.0.x. Adding explicit binaryTargets ensures the correct query engine is always generated regardless of build host. Also removes inline comments from .env.example rate limit values — Portainer treats trailing comments as part of the value. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -3,6 +3,7 @@
|
||||
|
||||
generator client {
|
||||
provider = "prisma-client-js"
|
||||
binaryTargets = ["native", "debian-openssl-3.0.x"]
|
||||
previewFeatures = ["postgresqlExtensions"]
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user