@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—
My WeWeb app is live on a specific domain
WeWeb uses my live Xano API by default
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).
Hi friends! Is moving from the Xano plugin to the REST plugin still the recommended way to manage working across branches with Xano as backend? Or is there another way to work with/hack the plugin so we can keep using those nice picklists?
can you let me know if this will be possible? trying to avoid needing to copy/recreate new WW environments to ‘carry over’ and deploy changes – especially because updating the production domain then becomes a bit tricky within WW (unless I’ve been doing it wrong).