Is there a recommended way to set up github actions for continuous delivering database migrations?
I want to set up proper CD in my project, starting from database migrations.
Is there a recommended way to implement that with GitHub Actions, considering that I'll be deploying on Supabase?
1 Reply
Hi @Sergio Visinoni. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the provided knowledge sources, there isn't a specific guide or recommendation for setting up GitHub Actions for continuous delivery of database migrations in a Wasp project. However, there is an open issue (https://github.com/wasp-lang/wasp/issues/602) on the Wasp GitHub repository discussing the implementation of a GitHub CI Action that builds your Wasp app, which could potentially be extended to handle database migrations.
For database migrations, there is an ongoing discussion on the Wasp GitHub repository about supporting data migrations and providing best practices and examples (issue #330 (https://github.com/wasp-lang/wasp/issues/330)). The discussion mentions the importance of a good migration workflow and documentation, especially for production environments.
When it comes to deploying on Supabase, there is a note in issue #1265 (https://github.com/wasp-lang/wasp/issues/1265) that a user was able to use a Supabase database via DATABASE_URL and it worked fine. However, the specifics of how this was set up are not provided.
For more complex operations like using Wasp with ChatGPT embeddings (pgvector), there is a workaround mentioned in issue #1215 (https://github.com/wasp-lang/wasp/issues/1215) that involves making the Prisma schema aware of the extension. This might be useful if you're planning to use similar extensions.
In conclusion, while there isn't a specific guide or recommendation for setting up GitHub Actions for continuous delivery of database migrations in a Wasp project, these discussions and issues might provide some insights and starting points. It's recommended to keep an eye on these issues for updates or to contribute to the discussions with your specific use case.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Sergio Visinoni, 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?