A broken system and a lost file are different problems. Understanding that difference makes it easier to choose the right recovery step when something stops working.
Reset repairs the environment.
A system reset replaces the operating system with a clean image. In Rootsy’s published reset behavior, /home, /root, and /srv are preserved. Other locations can be replaced, so check where your important configuration lives before you reset.
That can help when system changes leave the computer in a bad state. It is not a promise to undo every application change or restore something that was deleted.
Backups preserve the work.
A backup is a separate copy you can recover from. Source code in a remote repository is a useful start, but it may not include database contents, uploaded files, or local configuration.
Rootsy backs up each computer daily, but backups stay with the computer. Keep copies of what matters somewhere else too.
Start with a short inventory.
List the code, data, configuration, and uploaded assets that would be difficult to recreate. For each one, note where it lives, how you copy it, and how you would restore it.
Keep credentials out of public repositories. Use a suitable secure location for secrets and document how they are supplied to the application without putting their values in the instructions.
Try the recovery path before you need it.
A backup becomes useful when you can restore it. For a small project, that might mean cloning the repository into another environment, restoring a sample data export, and running the documented setup steps.
Make this part of how you maintain the project. The point is not a complicated ritual. It is knowing which action gives you a clean system and which gives you your work back.