Michael Udinski Cameron Booth Louis Machado Ray Deck
Okay - I THINK I finally have a process / flow for development across my team for separating a test / staging environment and a live / production environment in XANO + WeWeb.
I have two important questions that I need clarification on:
assuming I have made an alternative data source in Xano called "staging" - I now have "staging" and "live" data sources - and at any given time - I can run a MIGRATION and OVERWRITE all data in "staging" with "live".
When XANO is set to "staging" - I can run my v1 branch of logic on the alternate data - but tables are read-only - (which is a good thing)
My first (and most important question) is:
If I update a table in "live" - WHEN is it updated in "staging"??
Are the read-only tables in "staging" only updated when I MIGRATE??
Or .. .are they a dynamic mirror of tables in "live"??
example:
QA developer is currently running tests on "staging" with v1 branch.
Back-end developer makes changes to a table in "live" - let's say he adds a field to User table for example. Will the QA developer now see that field?? Or will he NOT see the field until we do another MIGRATION?
My other question is - on a SCALE plan - can I LOCK the "migration" to one or two specific team members??
And BONUS question (😜 ) is ... is there a way I can NOT ALLOW any migration from one specific source to another ?? So ... in my case ... I would like to LOCK DOWN permissions on migration from LIVE to STAGING to myself and one other backend dev - but also PREVENT anyone from migrating from STAGING to LIVE. I wanna make sure nobody ever overwrites the LIVE data source ... ever 😉
