How to Manage Dev & Prod Environments with Supabase

Ask us anything
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 Weweb + Pinecone + Xano, but for this specific case Supabase seems really convenient.

I started connected Supabase without that much trouble until… I’ve hit a roadblock: how to manage development and production environments between WeWeb 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 WeWeb (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

CLI is very simple to use. My favorite workflow is to create a local copy of my DB and spin up Supabase locally to then use migrations to move my changes to the production. It’s very convenient. If you would like a more hands on experience, I do teach this (Consult with Broberto – Broberto)