1
Versions of a Project
Source: supabase/supabase#12888 · opened by @inbytesdevteam
I know there are some suggestions on having an easy way to Duplicate Projects for staging purposes ( But it would be a nice feature that we don't have to do that anymore just to create a staging or testing environment. What if there was a way to create one project and it has a way to create different versions for Staging, Testing environments in the project. It has a way to migrate or update the DB as needed to prod with just a click of a button. API URL will be just the same URL except that it has -staging suffix or prefix attached. And have a way to rollback to past DB if possible. This limit the chances of making a mistakes in migrating/updating the db schema, RLS, etc to another project. This will make sure that the project runs in the same version of Supabase because it's possible that projects can have different versions of Supabase installed. And would be a game changer because it simplify the process of having multiple projects (for environment purposes) or…
No pledges yet. Be the first to back this.
Comments
Similar requests
Missing service versions in dashboards
2 votes · 0 comments
Request to Enable External JWT Authentication with Firebase (Project: dropnow-2025)
1 vote · 0 comments
Supabase DB reset --linked should display what the linked project is
9 votes · 0 comments
I'm a frontend developer and my experience with the backend is more just Firebase. I really like the Netlify feature, where I can add a config to the project and a button: "Deploy Own". Netlify puts up an instance of the project, asks for e
1 vote · 0 comments
an way to reset/rollback project database to the first version
11 votes · 0 comments
No comments yet.