I completely agree with you on this. Bubble needs to run a stable production framework that doesn’t receive any changes unless the community is given prior notice and preparation.
If they release an update to a dev/staging cluster then users would have an opportunity to report the bug and Bubble could fix it. Rapid iteration is very good and can be very bad if not done well. I think this policy should be given further consideration.
Two seemingly good options:
Lock production/live apps from receiving any changes without said notice
Allow apps to run on the current version OR the previous version of the Bubble platform. Then if they push a change that breaks, individual apps could choose to rollback to the previous version of the platform, report the bug to Bubble and switch back to the current version when the bug was patched/resolved.
Thanks for the update. Could you share what the followi g goal will allow?
“For the overhaul of our network architecture and infrastructure, we are starting with improving our credentials and configuration management, and aim to have our first production system using the new configuration management by the end of the month.”
Is it for stability or will it open new posibilities?
Any ETA when this will be available?
Choosing an own AWS region would be helpful. World is changing pretty fast and most of my clients wants to store their data close by. It’s a bottleneck at the moment.
Really like you are prioritizing the UI. Here’s a bit of feedback and improvement suggestions to the frontpage amongst other things. Would love to do a second round overhaul myself as a UX nerd but hope your team can use it
Would love to know when the regional servers are going to be implemented and if there are expected speed gains to be had if for instance I’m in Australia on an Australian server
Having my app on a server in my region would increase the likelihood of me upgrading to a higher plan significantly. Why upgrade capacity if the region issue is having over your app in the first place. That is at least true in my case.
So this something thats going to be something that is similar to reuseable elements? just updated? (with new ways to pass state or something similar, with option for nested components? or am i on completely wrong track)