[Chrome Extension] Supabase Live and Staging

Developer corner
1

Hello everyone, I see some people struggling with using WeWeb and Supabase with a Staging/Production DB separated, as now it requires to always switch credentials. I’m writing this post mostly to:

  1. Sort of see how many people are building with Supabase are affected by this issue - eg. if it’s worth tackling.
  2. Ask the WeWeb team - most probably @Alexis - whether there is a fix in sight - eg. again if it’s worth tackling, or if the issue is gonna be fixed soon and I should direct my time/effort elsewhere. If it’s planned in a month, then there is no need to make a solution for it.

I’m considering doing some exploration and offer a patch for this issue via a Chrome extension that will attempt to modify the requests with the URL and API keys. I’m not still sure about Auth, as apparently WeWeb handles that on their side, but at least the plain Supabase part of things could be doable.

2 Likes
2

In the short term roadmap we have a feature that will allow everyone to define plugin settings by environment (tabs editor / staging / production in plugin settings), it should handle your usecase

4 Likes
3

That’s really good to hear. Just how short term are we talking, exactly? Because this is a HUGE deal for us

4

We really want to achieve it this summer, there is many new features in development right now and we have to release them first, env management should be part of the next one!

5

Is there any update on this? Having to manually change my supabase credentials so that I can have true staging and prod environments doesn’t feed very “production-grade.”