We work on shared Bootstrap Studio projects stored on a network drive. When one user opens a project, another user receives no warning that it is already being edited. This makes it easy to overwrite each other’s work.
We need a built-in feature that detects when a project is in use and displays a warning, preferably identifying the person editing it. A second user should be able to open the project in read-only mode, and the lock should be released automatically when the project is closed.
This request was already raised in a forum post in 2019:
Many updates have been released since then, but we still haven’t found a built-in solution to this problem. Manual coordination and separate launcher applications are cumbersome and prone to mistakes.
We are asking for basic project locking to prevent accidental overwrites. Is there currently a way to achieve this in Bootstrap Studio? If not, do you plan to implement it, and when could we expect it?
Syncing without a central server and relying on network storage is brittle, but could be done in a limited fashion like showing a warning to the user that the design is opened by another instance. We’ll need to see more people ask for it before committing to do it. So if others would like to see it, write below.
I would be opposed to any BSS model that makes the application “cloud-based” - even if it afforded the ability for multiple users to edit a site at the same time.
agreed with @printninja , at least on project level, that’s sounds like bad idea…
as for my proposed middleground would be to update the online components…
instead of name, allow to use unique id;
add simple auth to access;
auto sync(always override with new one, no versioning, it’ll just become too complicated without server functionality dedicated to it):
auto download for importer;
auto upload for exporter;
allows non element components, such as for cms admin, share cms values/metas/tables/whatever dev going to name it;
Thanks for the replies. In the meantime, we wrote our own launcher that warns when a project is already open. It works perfectly for us, so the topic is closed on our side.