Hi all,
I am about to launch my first weweb platform and have already another one baking in the oven and hopefully 2 more in the future. But hoping some clarifications will make it easier I don’t have to hit a bank .
I have scavenged through almost all topics here regarding the plans and some things are not clear yet:
If I purchase the annual plan and export one app to my own frontend hosting, does this mean I can have 2 apps running (One weweb, one in self-hosting)?
Or only 1 Live app is allowed no matter where it is hosted?
What is the dependency on Self-hosted? Will still anything go through weweb servers? Or just when I make updates to the frontend and deploy to PROD?
You will still need the editor to “edit” and export the app again. So it depends. But in theory you can have infinite amounts of the same app, if you self host and host it infinite amount of times, if that would be a usecase. The workflow to make any edits would be
Make the changes in the editor → Publish → Upload the latest version
You also can automate this (even though I’m not sure), it should be possible to use the Webhooks WeWeb provides to simply go and do this for a CI/CD automated pipeline.
I’m not sure about the things that require WeWeb’s server, but the exported app is basically a Vue.js package that you can simply throw anywhere, even run locally without any setup since last update. As for the server-side things like routing the REST for CORS, or OpenAI etc. I’m not sure.
@Slavo will be the best source of truth for this, at the end of the day, he’s Mr. WeWeb
Hi @Broberto,
In my case, they would be 2 different apps. Thus if possible to have an App X self-hosted and an App Y weweb hosted. So 2 different custom domains.
It would make sense the server-side things, unless of course the export would be a total “blueprint” export. I am fine either way, I will always use weweb as editor, but just to keep in mind the architecture when building. Thanks.
The way it works now is that you have one app in the editor, and you can self host that app, on a domain X, Y, Z or any else however many times, since you have the project files. Self-hosting an app and then building an another one on the same project won’t be doable I think, since you need that app to live there so you can make edits. So the rule would be, two completely different apps (e.g My Groceries App and The HR Bombastic App) would require two separate projects.
You can deploy the same app to as many domains as you want - manually. If you have have different apps, you need need different subscriptions.
If you want to automate the deployment (have a CI/DC type environment), you need access to the self-hosting API (Enterprise Plan only)–> you can write scripts that automate the deployment process.
There is no dependence on WeWeb whatsoever. Your app runs on your infrastructure and makes API calls directly to your backend. No traffic passes through WeWeb, there is no backdoor access or some umbilical that would connect your app to WeWeb. Literally, if WeWeb was to disappear, your app would continue running.
Your self-hosted app will keep running even if you stop paying the subscription. You only need the subscription to continue developing and maintaining your app in the Editor. While you can export the raw code of your app (HTML/CSS/JS) as well as the compiled vueJS app, the code is create by a machine for a machine and as such it is not structured the same way a human dev would structure it. So developing the app code outside the editor, while theoretically possible, would be very hard.
Authentication is now (since June) handled through front-end so there is no need to go back to the Weweb server for auth purposes.
In general, everyhting that @Broberto says above is 100% correct, he knows WeWeb better than all of us.
As far as I can I will always support Weweb, it was more a scalability vs Bootstrap products launch strategy. Need to rethink strategy to launch multiple products in this case.
.
.