Hey guys!
I’m trying to understand how backups work.
I’m building a new feature, which is a large effort. We still don’t know if our users will like this feature, so I want to be able to roll back to an old version if we want to.
I saw that when rolling back to an older version, you lose all the progress after that version. I was wondering how can I save the version without the new feature, and be able to rollback if needed, without losing my work.
Thanks!
Nico
Hi Nico!
It seems to me that you are talking about branching, which is a feature WeWeb doesn’t support right now, so here’s how backups function and what you can do to keep your work safe:
- What Backups Do:
When you roll back to an older backup/version, everything you built after that point is removed. It’s a full overwrite—your app/project becomes exactly as it was at the time of that backup.
- How to Work Safely:
If you want to save a version before your new feature, and don’t want to lose your progress on the new feature, here’s what you can do:
- Create a Manual Backup:
Export your project (if possible) or clone your project manually using WeWeb’s export or duplication feature (if available). This creates a separate copy you can revert to at any time.
- Workflow Example:
- After finishing the stable version (before the risky new feature), make a manual backup.
- Then, proceed to build the new feature in your main project.
- If you later want to remove the new feature, roll back to your stable backup or import the exported/duplicated copy.
- If you need any work from the new feature, you’ll have to manually copy/export those pieces from the project where you built it.
- Take Frequent Backups:
Before major changes, regularly save backups so you always have recent restore points.
- No Merge Option:
There’s no way to merge changes from two versions, so anything built after a rollback will be lost unless manually copied out.
Hope this helps