Supabase - switching keys from staging to prod affects filters

[cdev]

I’ve been using two Supabase projects as a staging and production environment.

I typically stay on staging, then put in the prod keys to Supabase and Supabase Auth plugins to publish my project.

I’ve noticed that when I do this, it seems like some of the filters on my collections are missing, and collections have errors or aren’t returned properly.

Is there a better way to manage this process? Can I be sure somehow that my collections will remain the same? I ensure that the two Supabase databases are in the same state before moving.

[Broberto]

You might wanna check this out, it’s non destructive, as it doesn’t interfere with WeWeb in any way, it just modifies the requests.

[Supabase] Switch between Production and Staging in one click

Preface Since I kind of opened this discussion a few days ago, in this thread [Chrome Extension] Supabase Live and Staging I actually found a really neat way of doing this, at least while WeWeb rolls out their own solution. This solution also doesn’t account for the part where WeWeb uses the Private - Secret keys to fetch things like fetching the users etc. What does this work on? Fetching the tables within your collections creating process a.k.a it can introspect your DB’s schema Changing th…