prisma client issues with monorepo workspaces
Not quite sure how to fix this, it can't seem to find the prisma client?
64 Replies
Project ID:
893df018-6917-4ca3-b43d-6db80b4819ca
Railway
404 - Page not found
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
I tried copying over my Dockerfile from my other bun/prisma project but that failed too
but I have turbo in my package.json? so I'm confused on why it's failing
build logs please https://bookmarklets.up.railway.app/log-downloader/
you can send files in discord too 😆
sorry, i was just trying to copy it without a bookmarklet 😅
may i quicky as why no bookmarklet?
honestly, i don't know how to use bookmarks on arc
i'll past the js into console
i havent heard of anyone using bookmarklets on arc
do you have a root directory set?
oh perhaps not
i don't see an option for that?
just asking to gather info, not an actionable question, but the root directory setting is in the source section of the service settings
can you send the package.json in your root?
OH
wait
found the root directory option
unless im blind, no priama there, so its not going to be installed
there's prisma in the server package.json
oh wait
exactly, so you will need an install command that installs the deps from the server app
i don't have a build script
although
im sure that can be one of the issues, but its not the issue
bun should install all deps from root tho
doesnt seem like it is on railway, besides even if it did, would you want to install deps from the client?
could this be a case of railway running an old bun version?
my bun / turborepo / workspaces knowledge is rusty
i know in my other prject that's similar I swapped to a dockerfile
and mine is non existent
Dockerfile is always an option, would get you the latest bun version on every deploy thats for sure
so i added the dockerfile
and i'm getting exec turbo not found
and so to be honest
I'm confused on how my old code is working lol
is what I have right now
how do you know the dockerfile is being used?
it gets used by default i thought
i mean yeah but you still gotta make sure
hmm
this should be install turbo
where is that dockerfile located?
root
you dont have turbo in the server package.json
the server doesn't need it
but you are trying to use it
it should only be needed in the root level package.json from my understanding
since bun installs
you are cd'ing into the server directory though
i removed that
(bun ignores the cd anyways, and just installs the whole workspace)
right now i get
theres still cd there, please remove
which?
cd /usr/src/app
do i not need that for the CMD to function right
no, its set by
WORKDIR /usr/src/app
try moving turbo out of dev deps
hmmm im running out of ideas
i found the source of all my pain
and got it working
Solution
i had a custom start command overriding the one i had in my dockerfile
conductors getting metadata about the users service can't come soon enough
thnks for the help in finding it!
happy to help where i can