Managing staging and production environments

[isaacmartin]

Staging environments are typically strongly decoupled from production ones. Thus, it would be expected to have different database and api resources in the backend ready to power these different environments. What is the recommended way to tell weweb to use a specific api domain when in stage vs production, for the api calls powering our weweb collections?

[Broberto]

For now, if you’re using Xano, you can use their branching. If you’re using anything else, you can use my “workaround”, the enviroment handling is coming and it’s on the list of features the team is working on I think. My workaround is for Supabase, but really, it’s same for anything if you’re savvy enough.

[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…