Choosing rclone mount vs bisync for Dropbox replacement

Описание и применение

Выбор между rclone mount и bisync позволяет пользователям заменить Dropbox, сочетая локальную скорость и офлайн‑доступ с управляемыми конфликтами и контролем за использованием диска.

Задача

Users need a local folder that behaves like Dropbox’s desktop client but with better control over latency, offline access, and disk usage.

Результат

By running bisync for the working set and mount for the archive, users gain local‑disk performance, offline access, and controlled conflict resolution while keeping cache size manageable.

Рабочий процесс

• 1. Identify working set (files edited daily).
• 2. Configure rclone bisync for the working set with a 5‑minute timer and an initial --resync.
• 3. Set up rclone mount for the archive with --vfs-cache-mode full and a capped cache size.
• 4. For multi‑device users, bisync each device against the remote and expose the server folder via rclone serve webdav.
• 5. Adjust --check-access and --transfers for metered or flaky connections.
• 6. Monitor cache usage and schedule bisync runs to balance API calls and divergence window.

Доказательства

rclone bisync gives you genuine local copies with local disk latency and true offline access, at the cost of a scheduled run, a mandatory first --resync, and conflict files you have to resolve yourself.

Источник

An rclone mount with --vfs-cache-mode full gives you a folder that looks complete in your file manager, but every first read of an uncached file costs a network round trip, and nothing is available offline until you have opened it.

Источник