desync(1)

πŸ“¦
version 1.1.5 Β· 3 versions
, in arch rolling

🌸 desync(1) β€” no literally bestie, this is the prune page πŸ’…

Okay so real talk: the man page header says desync(1) (that's the family name, the whole desync squad 🫢), and this specific page is all about desync-prune. Yes, the pruning one. The "delete the stuff nobody's using" one. Buckle up πŸŽ€


✨ NAME ✨

desync-prune β€” remove unreferenced chunks from a store πŸ§ΉπŸ’–


⭐ SYNOPSIS ⭐

desync prune <index> [<index>...] [flags]

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the vibe: desync reads chunk IDs out of your index files, then deletes every chunk from a store that isn't referenced in any of the index files you handed it. That's it. That's the whole job. Iconic.

⚠️ Heads up bestie β€” this is a destructive operation. Like, chunks-gone-forever destructive. So by default you get a confirmation prompt before any chunks get yeeted, unless you pass --yes. (Use --yes responsibly, iykyk πŸ™ˆ)

Also! You can pass - to read a single index from STDIN. Lowkey handy. 🌈


πŸ’… OPTIONS πŸ’…

  • --ca-cert="" β€” trust authorities listed in this file instead of the OS trust store πŸŽ€
  • -r, --cache-repair[=true] β€” replace invalid chunks in the cache from source ✨
  • --client-cert="" β€” path to the client certificate for TLS authentication πŸ”
  • --client-key="" β€” path to the client key for TLS authentication πŸ”‘
  • -n, --concurrency=10 β€” number of concurrent goroutines. Set it to -1 and let desync choose for you: the number of CPUs for chunking and hashing, adapting to each store up to 128 for transfers ⚑
  • -e, --error-retry=3 β€” how many times to retry when a network error happens 😭
  • -b, --error-retry-base-interval=500ms β€” the initial retry delay, which increases linearly with each subsequent attempt ⏳
  • -h, --help[=false] β€” help for prune 🫢
  • -s, --store="" β€” the store you wanna prune πŸ—‚οΈ
  • -t, --trust-insecure[=false] β€” trust invalid certificates (yes, that's what it says πŸ‘€)
  • -y, --yes[=false] β€” do NOT ask for confirmation before deleting chunks. main character energy, use with care πŸ’€

πŸ‘‘ OPTIONS INHERITED FROM PARENT COMMANDS πŸ‘‘

  • --config="" β€” config file (default $HOME/.config/desync/config.json)
  • --digest="sha512-256" β€” digest algorithm, either sha512-256 or sha256
  • --verbose[=false] β€” verbose mode πŸ—£οΈ

πŸ”₯ EXAMPLE πŸ”₯

  desync prune -s /path/to/local --yes file.caibx
  desync prune -s /path/to/local current.caibx previous.caibx

First one: prune with zero questions asked (--yes, bold of you). Second one: prune using two index files at once so it keeps anything referenced by current.caibx or previous.caibx. Slay 🌸


πŸŽ€ SEE ALSO πŸŽ€

desync(1) β€” go say hi to the parent page, it misses you πŸ’œ


πŸ’– HISTORY πŸ’–

20-Oct-2026 Auto generated by spf13/cobra β€” yeah, the robots made this one πŸ€–βœ¨


And that's the whole page, bestie β€” you're officially a prune girlie now πŸ§šβ€β™€οΈπŸ’…

Sign-off time: this was desync, Oct 2026 vintage, filed under desync(1) πŸ“

πŸ“¦ where this page comes from