@Quentin how does WeWeb’s native Xano integration handle branching? I’m guessing with the current integration that WeWeb always use the live branch. Is there any way to use a non-live branch in a project?
Here’s how I’m currently thinking through an ideal setup—
Live/production environment
My WeWeb app is live on a specific domain
WeWeb uses my live Xano API by default
Testing environment
I think I would need an additional custom domain so I can copy the live project, publish it to “dev.testing.mywebsite.com” (or something similar), and begin making edits and publishing those edits to dev.testing.mywebsite.com so I can test them in a “real” environment.
When I’m ready to go live with this version, I would need to remove the live WeWeb’s domain and add it to the new WeWeb app.
Ideally, there would be a setting on the WeWeb<>Xano integration (under Xano in the plugin settings) to configure WeWeb to work alongside Xano’s versioning logic. IE, I could select which version I would want to use, and if I selected one of my non-live branches (such as branch v2), WeWeb would add :v2 to all API endpoints
From what I can tell, everything above is possible except for the bolded “Ideally…” component, but I’d love to hear from someone on the WeWeb team to confirm (or suggest a different route).
Adding the need to the roadmap for Xano. In the meantime, I suggest using the REST API plugin and concatenate based on a variable containing the API base URL, and change it when in prod.