-
Anyone else managed to update to 1.26.0 on FreeBSD? I'm a couple of hours into trying to make this work, beginning to flail, and considering rolling back to 1.24.1, which was fine. After various false starts I've finally updated the locally built copy of prisma-engines to 3.9.0 (there is no 3.9.2, and as any FreeBSD Umami user already knows, npm flavour prisma does not support FreeBSD) but now, even with my own prisma-engines, when I come to run
Looks like it's no longer enough to build prisma-engines but you have to build the whole of prisma too? yay |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
@wgmyers What you can do is rollback prisma itself to the previous version
☝️ this pins the version to 3.6.0 |
Beta Was this translation helpful? Give feedback.
-
Thanks, MIke. After three hours tearing my hair out I just found the answer. My bad for thinking, oh I'll just quickly run this upgrade at midnight. Bad idea. Turns out that Prisma have changed their required environment variables for custom installs, and now you need to specify whether you are using libraries or binaries via two new env vars. Also, for some reason, something somewhere (dotenv? prisma?) no longer likes it when you have more than one Anyway. The solution is to add something like the following in
Note the first two - these are new since I last had to do this. Now prisma knows what kind of files it is looking for and can also find them. |
Beta Was this translation helpful? Give feedback.
Thanks, MIke.
After three hours tearing my hair out I just found the answer. My bad for thinking, oh I'll just quickly run this upgrade at midnight. Bad idea.
Turns out that Prisma have changed their required environment variables for custom installs, and now you need to specify whether you are using libraries or binaries via two new env vars. Also, for some reason, something somewhere (dotenv? prisma?) no longer likes it when you have more than one
.env
file floating around and complains. I had two, one for umami and one for prisma in the prisma directory. The latter was no longer being read, hence Prisma swearing up and down that it had no binaries and didn't support FreeBSD. (It's fine…