Hi everyone,
I built an open-source tool called Bisync Hub to help manage bidirectional syncs with rclone bisync.
The main pain point I wanted to address was how sync errors and safety stops are handled. When TOO_MANY_DELETES or conflicts trigger an abort, parsing the raw logs and deciding whether to run --force can be risky.
Bisync Hub provides a local dashboard to inspect and resolve those situations safely:
- Conflict & Deletion Review: Inspect trapped aborts and choose whether to accept deletions or restore files before committing the sync.
- Conflict Analysis: Checks file sizes, timestamps (e.g. DST clock skew), and common lock/temporary files to suggest resolutions.
- Single Binary: Written in Go with an embedded Alpine.js web UI (single binary, no external runtime dependencies).
- Rclone-Native: Interacts directly with standard Rclone commands and work files. Tested primarily with Google Drive and OneDrive.
Project links:
- GitHub: GitHub - slemmercs/rclone-bisync: Autonomous bidirectional sync engine and control plane for Linux. Real-time Rclone RC integration, safety circuit breakers, interactive sync review, and cryptographic immutable audit ledger. · GitHub
- Docs / Demo: Home | Bisync Hub
Would love to hear feedback or thoughts from the community!