Self-hosting + WeWeb Public API + Cloudflare self-hosting guide - documentation release

Hello everyone!

We have released some updates to our self-hosting and code export articles.

What has changed:

Please leave your feedback. :slight_smile:

6 Likes

Reminder: feel free to share your feedback :slight_smile:

1 Like

Amazing, thank you! We’ll dig into this .

1 Like

for the public API, which plan is necessary?

i have an app that uses static collections and i need to trigger a deployment workflow after an item in my backend has changed to a certain state (could also do a timed deployment once a day - this would also be feasible on my side).

Hi @jayjay13 :wave:

It’s only available for Enterprise customers.

are there plans to to make features like this available as add-ons for non-enterprise users? would love such a feature to automate the deployment pipeline… otherwise i probably will have to use some sort of web scraper/browser automation tool to perform this actions…

Thanks for the docs - really helpful. I’m planning to use BunnyCDN instead of Cloudflare and have a general understanding question. Does the CDN know what files are statis (can be cached) and which ones are not (like forms, user specific data)?

Let’s say in my WeWeb application, there are a lot comments by users created in realtime. These should be served instantly and could not load from a cache. How would that work with Cloudflare/Bunny or any other CDN?

Hey @danlopes
quick follow up regarding this. Since the last update to the deployment system, the process is way faster. I read somewhere that the public api to deploy an app was restricted to Enterprise customers only due to the high computing power/resources needed for the deployment. As this is now way quicker, will the api access change in the future?

Why would yo need API anymore if you can simply use Github and Github Actions?

after the deployment for sure but to get the latest state it into the Github repo I still need to deploy, right? or am I missing something?
(main “problem” is that i use a static collection - as of now there is not really a benefit to this anymore which is why it maybe makes sense to switch to a dynamic one with the dynamic metadata… :thinking: )

Please review new export feature
You use “:” for css file name which cause error 0x80070057 on windows, please fix it. :roll_eyes:

Hi @jayjay13 , access to the publishing API is only available on the Enterprise tier. The recent changes to the publisher do not change that. If you are interested in the Enterprise plans, let me know.