stiva

stiva moves large files out of a cloud-synced folder onto another disk, and leaves a readable breadcrumb saying where each one went.

The problem it was built for

Twenty gigabytes in Google Drive, the paid plan about to run out, and half that weight is material untouched for years. You move it to an external disk. Six months later you no longer remember which disk, or why, and the file is not where you go looking for it.

What it adds over rsync

rsync and rclone do copy, verification and source deletion better than this could, and stiva does not try to redo them. What it adds:

• A declarative plan you read and approve before anything runs, with the reason written next to each item.
• A readable breadcrumb left where the content was: <name>.MOVED.md next to the gap.
• A cumulative manifest, so find and restore work months later.
• A preflight that recognises cloud-only stubs (on APFS, st_blocks at zero) and refuses Google-native files, because without a checksum they cannot be verified.
• A gate that writes the trail before the removal, never after.

Honest about the alternative

The closest existing tool is froster, and the README says so: if archiving to S3 object storage is enough for you, use that instead. stiva exists for the case where the destination is a disk you can hold.

Site · Agent manual · Source