Remix Indie Stack: How to Reset Staging and Main Databae

I just had a failed migration in my staging development for a fly.io indie stack deployment.

I know it’s because I changed the schema after there was already data in the tables and the new schema is not compatible with the existing data.

In local development, all I have to do is prisma migrate reset , then run the new migration, but, I’m not sure how to execute that in staging or main ?

Do I need to drop the volume and create another? Can I run a prisma command on the fly volume from the flyctl ?

I’m sure this is a common problem, but, haven’t been able to find any clear path forward.

@keepforever what was your ultimate solution for this? I’m still trying to figure out where in the indie-stack deploy it runs the migrations on staging/prod.

Hey @cayblood ,

I was never able to find a solution for this (tho, I’m sure one must exist).

What I ended up having to do was delete the fly.io project and start over and stand up a new one.

Now I’m just very careful to always make backward-compatible migrations.

Good luck!