Setting up database migration workflow (through Supabase CLI and possibly Snaplet) A live project had a faster pace than anticipated, and that's why up until now all schema migrations have directly been applied to the live database through SQL statements. We would now like to set up a dedicated migration workflow for database changes. Where they are first applied to a local development database, and then committed to the production database. I tried it myself so far but stumbled upon some problems, mainly because the production database has grown quite large already (multiple schemas and roles) which is why - I believe - the initial migration gathered through

supabase db remote commit

is failing. Ideally I'm looking for a pair-programming session with someone who tutors me through setting up this workflow. To seed the development database, we'd ideally setup a [Snaplet](https://supabase.com/partners/snaplet) workflow in this same session. If interested, please DM me 🙂

if you find someone, we also need help with the same