Deployed app on fly.io, tables created, but no data seed applied

[greg]

Hi,

Ah, this seems to be a common problem e.g

can't seed staging DB with remix blues stack

Hi, I am using Blues Stack . but having an issue with seeding db which deployed to fly using command flyctl deploy --local-only. locally db seeded successfully. deployed to staging working fine but DB is empty. any help here will be highly appreciated. if you need any further information please let me know. here is a copy of my fly.toml app = "restaurant-recipe-manager-staging" kill_signal = "SIGINT" kill_timeout = 5 processes = [] [deploy] release_command = "npx prisma migrate…

Do any of the suggested solutions in this thread work? It seems like what worked for one guy didn’t for another, oddly! Maybe the one at the very bottom?

Running npx prisma db seed after deployment

I’m able to deploy a remix app, however its not running my seed.ts file (per the Remix | Jokes App) instructions. I’d like to run the seed.ts on the deployed instance after the deploy has finished. I’m able to ssh to the app and run npx commands, but when i run “npx prisma db seed” I get the error: Running seed command node --require esbuild-register prisma/seed.ts … node:internal/modules/cjs/loader:936 throw err; ^ Error: Cannot find module ‘esbuild-register’ Require stack: internal/pr…