How to Manage Dev & Prod Environments with Supabase

Need help Database
1

Hi everyone!

I’m considering using Supabase as the backend for a client project that involves handling a large dataset and requires vector search capabilities. Initially, I thought of using Bubble + Pinecone, but for this specific case, it seems too WU-intensive.

I’ve experimented with two plugins, Nocodegarden and Supabase.js, and found them really impressive! I managed to set up authentication, real-time features with WebSocket, database queries, and file uploads without too much trouble.

However, I’ve hit a roadblock: how to manage development and production environments between Bubble and Supabase. After some research on YouTube, I noticed that Supabase’s branching system seems to require CLI/Git skills, which feels a bit overwhelming for my current skill set.

Here are the two options I’m considering:

  1. Using two database schemas: Use the default public schema for production and create a staging schema for development, passing it as a variable in Bubble (Supabase.js supports schema customization).

  2. Creating two separate projects: One for production and one for staging. However, this seems inefficient and difficult to manage in the long run.

Has anyone found a good workaround for this? I’d love to hear your thoughts or experiences!

Thanks in advance! :blush:

2

Create 2 separate projects will be more secure and will really separate your data.
That’s what’s recommended.

On the other hand, you have to make sure that both DB schéma are the same. So, I would only create the live project db when you’ll be (pretty) sure about the db to avoid changing live too often