Hi team,
I am looking for an option of copy on write support for Supabase branches. The idea is to create ephemeral branches from my main Supabase environment. The objective is to run end to end integration tests while running CI on that environment and provide a branch for the developers to work on-demand. Currently I will have to create a branch and restore the entire database and considering the size of the database is upwards of 29 GB uncompressed, which will take a lot of time to restore, thereby making this an impossible solution. Using copy on write with Neon DB is an option, but the challenge is the application depends on Supabase auth and supabase storage and supabase realtime, where I will loose the capability of testing these functionalities.
Would be looking for help from the community.
The user is seeking a 'copy on write' feature for Supabase branches to create ephemeral branches for CI testing without restoring large databases. They mention the challenge of using Neon DB due to dependencies on Supabase's auth, storage, and realtime features. The user is looking for community suggestions to address this issue.
Is there a need to use production data for development? Couldn't you create a seed file to add a small amount of seed data to each preview branch
<@1406214781911961631> the CI tests also run lot of under load scenarios as well, which would require that amount of data. Essentially think of it as one comprehensive test suite which runs multiple facets.
Ahh okay, i'll leave it to see if anyone else has any ideas. I haven't faced this issue myself nor can i find any known solution searching the docs