Hey all! Has anyone had success running Prisma on...
# prisma-client
j
Hey all! Has anyone had success running Prisma on AWS Graviton EC2 instances? What binrary target do I need to use for the engine? We currently have these options set:
Copy code
binaryTargets = ["native", "linux-musl", "linux-arm-openssl-1.1.x"]
but then once we deploy to AWS we get
Copy code
Error: Unknown PRISMA_QUERY_ENGINE_LIBRARY undefined. Possible binaryTargets: darwin, darwin-arm64, debian-openssl-1.0.x, debian-openssl-1.1.x, rhel-openssl-1.0.x, rhel-openssl-1.1.x, linux-arm-openssl-1.1.x, linux-arm-openssl-1.0.x, linux-musl, linux-nixos, windows, freebsd11, freebsd12, openbsd, netbsd, arm, native or a path to the query engine library.
We are using Prisma 3.0.1, I know this is older we cannot upgrade (without some more investigtion) because of this issue https://github.com/prisma/prisma/issues/10512 We have multiple prisma schemas in our Nx repo and upgrading to the newest prisma seems to break them. cause it is looking in a hard coded spot for the schema. Ideas?