Module backups 

Configuration backups in one place: the copies HelixForge’s scripts leave beside a file before changing it (<file>.commander-backup-<time>, <file>.helixforge-backup-<time>), found in the user’s configuration and in the system places those scripts change, and restored in a way that can itself be undone. Snapshots (Snapper, Timeshift) are taken before system changes where the machine supports them; HelixForge does not roll snapshots or packages back itself.

Structs

Backup

One backup copy and the file it was taken from.

Roots

Where backups are looked for: the user’s configuration (any depth, as the dotfiles installers leave them) and the system places HelixForge’s scripts change (shallow).

Enums

Snapshots

A snapshot tool the machine is set up for.

Functions

discover

Every backup under the roots, newest first.

parse_name

The original’s name and the time stamp, for a backup’s file name.

plan_restore

A plan that restores one backup.

restore_step

The step that puts a backup back: the current file, if any, is moved aside as a backup of its own first, so the restore can be undone too.

with_snapshot

Put a snapshot step first, taken before the plan’s other steps run.

worth_a_snapshot

Whether a plan changes the system enough to snapshot first: risk high, or a step whose entry changes privileged files, the kernel or disks.