Deploying without breaking changes
Hello !
I'd like your help in putting database modifications into production. I'm not sure I've understood the whole flow to avoid breaking changes.
For the context, I have a database in production with active customers and FastApi backend on DigitalOcean. I use my database locally to make changes before push.
When I make changes to my local database, I create migrations to push them to my production database, but how can I synchronise the deployment of my production database with my API? Because if one or the other is pushed beforehand, this is bound to create breakable changes (e.g. column name change or type change).
I've seen that it's possible to use the Github integration directly with Supabase and that it detects the migration files in the Supabase folder, but is this the right way in my case (note that I'm still on the free version at the moment)? Or do I need to create a CI/CD pipeline to orchestrate all this? Are there simpler ways?
Thank you for your feedback and I hope I've been clear enough in my explanations!
I'd like your help in putting database modifications into production. I'm not sure I've understood the whole flow to avoid breaking changes.
For the context, I have a database in production with active customers and FastApi backend on DigitalOcean. I use my database locally to make changes before push.
When I make changes to my local database, I create migrations to push them to my production database, but how can I synchronise the deployment of my production database with my API? Because if one or the other is pushed beforehand, this is bound to create breakable changes (e.g. column name change or type change).
I've seen that it's possible to use the Github integration directly with Supabase and that it detects the migration files in the Supabase folder, but is this the right way in my case (note that I'm still on the free version at the moment)? Or do I need to create a CI/CD pipeline to orchestrate all this? Are there simpler ways?
Thank you for your feedback and I hope I've been clear enough in my explanations!
