Migration Error after Fly.io deployment
I recently upgraded wasp from 0.13 to 0.14 and on recent deploys i have encountered an error that doesnt let my server go online. Here is an extract of the error my server logs is throwing:
8 Replies
Hi @Tomas. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Hmm, I don't know enough to give you a confident answer yet. To better assist you, could you please provide more details about the error message you're encountering?
In the meantime, you might find it helpful to review the Wasp documentation on database migrations (https://wasp-lang.dev/docs/data-model/migrations) and deployment (https://wasp-lang.dev/docs/advanced/deployment/cli).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Tomas, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
i think this is the key line of the error:
2024-10-10T19:03:37.217 app[784e22df203d28] scl [info] migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve
@kapa.ai
Let me check the knowledge base for you. One moment! :books:
Wohooo @Tomas, you just became a Waspeteer level 2!
Sorry @Tomas, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
fixed it! i went into my database and deleted the prisma_migration that had an error (that migration didnt exist in my local migrations)
Yup, seems you like have issues with database migrations. THere are handled by prisma, so I suggest checking their docs for more infromation on what caused it and how to solve it.
all right, that does it then! How did you get into that state though?
i think it has something to do with the upgrade from 0.13 to 0.14.. that messed up a few things in my migrations locally at least
and this started happening only after that upgrade
if anyone gets that error it would be enough to delete the row with the failing migration in the prod database 🙂