20b311e9-9f30-40a4-bbc2-2d5543030462

I wonder if its because the 2 commands are executing at once, is there a way to separate them maybe so railway understands they are like, different things? the bun build and the prisma generate

ah mb its with && i think

nvm fixed now

👍

why are you building and migrating at the same step

wait am I not supposed to do that? idk

Im new to this ORM

there's a pre deploy command for stuff like that

it works now tho

https://docs.railway.com/guides/pre-deploy-command

oh... whats its called in the package.json so I add it? you mean I should put the prisma generate in there yes?

ah

you define it in the service settings

ah yeah but I like to have everything in my package.json like build, start... isnt there one for the package.json?

I see on the link they seem to use migrate

yeah but it's not right, you need better separation of concerns and pre deploy commands run in an isolated container

like bun migrate I assume it would be with bun

ah

bun has nothing to do with your orm

yeah I mean the migrate command

or you mean "bun migrate" to run your package.json migrate script

yes 🙂

won't a railway.json work as well? https://docs.railway.com/guides/pre-deploy-command

Im used to package.json I rather dont change it

anyways I can just add a script in my package.json called migrate and put the prisma generate in there, yes?

and doesnt matter if i execute that script with npm or bun I know