Prisma deployment with NestJS and MySQL. Difficult company policies
I'm struggling with deployment here at work. I've got a NEST app that uses mysql and we're trying to implement prisma and I'm running into config issues and can't figure out a solution
- I can't download the binaries using my DOCKERFILE. The Azure instance that it runs on to build my app doesn't have access to binaries.prisma.sh
- my root filesystem MUST be readonly once the pod is up and running. I'm. noticing that prisma migrate deploy tries to write to node_modules directory and that fails because it is read only
I thought changing the engineType to 'client' would mean that only javascript was used but looks like the prisma CLI still needs the binaries to run?
If I use an output folder in my schema.prisma with binaryTargets that I need. I have copied that information up to git so that it's available during my npm install etc. Do I need to copy that information to node_modules after npm install? or do I tell prisma to use the binaries in my output folder so that it doesn't try to download from the internet? Seems like my deploy would still try to write information to node_modules though
I've been floundering for too long with this. Any help would be appreciated . Thanks
4 Replies
You selected the carefully hand-crafted route. A dev artisan will respond soon. Meanwhile, the
#ask-ai channel awaits if you're curious!try the rust free version with engineType = "client" it should not ask for the binaries
make sure to update to latest prisma and @prisma/client and mwsql dapter and generate (
prisma generate)
https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/no-rust-engineUse Prisma ORM without Rust engines | Prisma Documentation
Learn how to use Prisma ORM without Rust engines
If it still complains about the binaries let me know
Hi @Aman thank you for the response. Sorry for the delay. I have made the changes to use the no Rust engines but when I run prisma generate it's still trying to connect to binaries.prisma.sh. From my reading the CLI commands still need the binaries? Do I not need CLI commands anymore? I thought I would still need to generate and deploy etc for when the database changes?
The npx migrate deploy still needs a binary to do it's job apparently unless I can't find the documentation otherwise