BitTorrent Sync: Painless File Syncing without the Cloud

Productivity Sauce
Cloud-based file syncing services are a dime a dozen nowadays. Most of them store copies of your data on remote servers and charge for storage space. This approach has two major drawbacks: you have to entrust your data to a third-party service, and the more storage you need, the more you have to pay. The recently released BitTorrent Sync tool offers an alternative solution that solves these problems. Instead of relying on a central server for storing files and syncing them between multiple machines, BitTorrent Sync uses a peer-to-peer protocol to keep files in sync across multiple machines. This is a brilliant solution, indeed. You don't need to run a dedicated synchronization server, there is no storage limit, and all your data stays on your machines. Better still, BitTorrent Sync encrypts all the traffic to keep your data safe.
Deploying BitTorrent on Linux is as easy as pie. Grab the appropriate version of the tool from the project's website, unpack the downloaded archive, and move the btsync executable binary to the directory of your choice. Run then BitTorrent Sync using the ./btsync command. Point then your browser to 127.0.0.1:8888/gui to access BitTorrent Sync's web interface. Here, you can add the folders you want to keep in sync. When adding a folder, you have to create a secret, a randomly generated 21-byte key. This secret is used to link folders between multiple machines.
While you can use the ./btsync command to run BitTorrent Sync with default settings, this is not always a good idea, as this leaves the web interface unprotected. The solution is to create a configuration file and point BitTorrent Sync to it. To view a sample configuration, run the ./btsync --dump-samle-config command. You can use the sample as a starting point for your own configuration file. Here is what my configuration file looks like:
{ "check_for_updates" : true, "download_limit" : 0, "upload_limit" : 0, "webui" : { "listen" : "0.0.0.0:8888", "login" : "username", "password" : "password" } }
To start BitTorrent Sync with a custom configuration file, use the ./btsync --config /path/to/btsync.conf command (replace /path/to/btsync.conf with the actual path to the configuration file).
comments powered by DisqusSubscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you’ve found an article to be beneficial.

News
-
System76 Releases COSMIC Alpha 7
With scores of bug fixes and a really cool workspaces feature, COSMIC is looking to soon migrate from alpha to beta.
-
OpenMandriva Lx 6.0 Available for Installation
The latest release of OpenMandriva has arrived with a new kernel, an updated Plasma desktop, and a server edition.
-
TrueNAS 25.04 Arrives with Thousands of Changes
One of the most popular Linux-based NAS solutions has rolled out the latest edition, based on Ubuntu 25.04.
-
Fedora 42 Available with Two New Spins
The latest release from the Fedora Project includes the usual updates, a new kernel, an official KDE Plasma spin, and a new System76 spin.
-
So Long, ArcoLinux
The ArcoLinux distribution is the latest Linux distribution to shut down.
-
What Open Source Pros Look for in a Job Role
Learn what professionals in technical and non-technical roles say is most important when seeking a new position.
-
Asahi Linux Runs into Issues with M4 Support
Due to Apple Silicon changes, the Asahi Linux project is at odds with adding support for the M4 chips.
-
Plasma 6.3.4 Now Available
Although not a major release, Plasma 6.3.4 does fix some bugs and offer a subtle change for the Plasma sidebar.
-
Linux Kernel 6.15 First Release Candidate Now Available
Linux Torvalds has announced that the release candidate for the final release of the Linux 6.15 series is now available.
-
Akamai Will Host kernel.org
The organization dedicated to cloud-based solutions has agreed to host kernel.org to deliver long-term stability for the development team.