Join the Webstudio community

Updated 9 months ago

Handling external connection breakdowns in webstudio

At a glance

The community member asks what would happen to their site if they set an external connection to a database or CMS and then broke something outside of Webstudio. The comments suggest that the site would likely break immediately, though it could potentially work for a while due to caching. Some community members recommend using static sites, which don't break as easily but also don't scale as well. Others suggest strategies for managing changes to the backend while a live site is connected, such as making non-breaking changes, migrating clients, or testing changes in the builder before switching the backend and frontend. There is no explicitly marked answer, but the community members provide several suggestions for best practices in this scenario.

If I set an external connection to a DB or CMS and then break something there (outside of Webstudio), what happens to my site? Would it rebuild broken, not rebuilt at all or something else?
O
J
15 comments
  1. I would expect the site to break, right away
  2. Could potentially work for a while due to caching
Good to know, thanks.
That's the price of live data
Static sites don't break that easily but they also don't scale as well
Would you have a recommended "best practice" for using development data vs live data outside of Webstudio but connecting to it?
whats the scenario?
I'm going to try to setup a multi-tenant instance of PayloadCMS. I've connected individual instances before.

But later if I want to add a feature to that structure, I'm assuming I'd probably break things on that end. I wouldn't want to break live sites that I've previously setup with it.
So the scenario is that you want to change how your backend works while a live site is connected to it
Yes, potentially. I'm open to better ideas though.
it sounds mostly like a backend problem.
There could be different strategies
  1. make the change non-breaking
  2. migrate client
  3. remove backwards compatibility
this would be a defacto standard
but its more complex
simpler one:
  1. test the changes in builder
  2. then in one go switch backend and frontend
potentially quick downtime
Thanks for the suggestions. I'll review these options and see what makes more sense for me. Appreciate the help.
Add a reply
Sign up and join the conversation on Discord