Repository navigation
Releases
OurSync 1.0.0
Google Drive on Linux Mint: your whole Drive at ~/Drive as an ordinary folder, streamed as you read it, synchronised both ways, with the files you choose kept on local disk and never evicted.
Install on Linux Mint 22 / Ubuntu 24.04 or newer.
Install a current rclone first. OurSync needs rclone 1.67 or newer, and cannot use 1.68.0. Mint 22 and Ubuntu 24.04 ship 1.60.1, which is below that, so the package will install but OurSync will refuse to mount until rclone is newer. This is rclone's own recommended route and takes a few seconds:
curl https://rclone.org/install.sh | sudo bashThen:
sudo apt install ./oursync_1.0.0_all.deb
oursync setup
systemctl --user enable --now oursync-mount.service
systemctl --user enable --now oursync-refresh.timerThat floor is measured, not guessed: below 1.67 a save to a pinned file reaches Drive but not the local copy, and 1.68.0 alone cannot read the mount's control-port address from the environment. Both failures are silent, so OurSync refuses rather than letting either happen quietly.
oursync setup walks the one-time Google Cloud step. OurSync ships no OAuth client ID, because an application distributing its own with Google's restricted drive scope needs OAuth verification and an annually renewed third-party security assessment. A client from your own Cloud project falls under Google's personal-use exemption instead, with an API quota nobody else is sharing.
Verified for this release
Against the real Google Drive on Linux Mint 22.3, with the packaged build installed from this .deb:
tools/acceptance-test.sh— 57 of 57, run three times: twenty awkward filenames, a zero-byte file, five levels of nesting, a megabyte of binary byte for byte, pinning a directory, a two-sided conflict reported and neither copy touched, a modification time ten years in the future, a mount restart, the rclone process killed outright, and the arguments a person gets wrong.tools/live-write-test.sh— 15 of 15: create, edit, repeated saves inside the write-back window, 24 MiB byte for byte, rename, delete recoverable from Drive's trash, and a remote change pulled into a pinned copy.tools/rclone-floor-test.sh— 20 of 20 on rclone 1.67.0, 1.68.1, 1.68.2, 1.70.3 and 1.76.0, with every unsupported version refused by name.
Known limitation worth reading
A file saved into ~/Drive while the mount is down goes to local disk, not to Drive, and is hidden underneath the mount when it returns. This is how every FUSE mount on Linux behaves; nothing is destroyed, and the mount restarts itself in about 15 seconds after a crash. oursync doctor says whether it is up. The README's "What it does not do" has the rest, including no differential upload — editing four bytes of a 2 GB file means re-uploading 2 GB, which no public Drive API offers a way around.
Free software under the GPL, version 3 or later. Not a Google product, and not affiliated with Google.