![]() Sudo cp /lib/systemd/system/Īnd now we can use the systemctl command to start the service and enable it at startup. cd syncthing-linux-amd64-v0.14.52/etc/linux-systemd/system/ ![]() What I did was I copied the file to the directory /lib/systemd/system. The tarball comes with systemd unit file so that users can enable it at startup and let the systemd to manage it (e.g. After that just unpack it and move/copy the binary to /usr/bin To get the latest version, head to its GitHub releases page, then grab the correct binary. No dependencies required, no additional packages needed. Just download the binary, make it executable, place it in $PATH, and it is ready to go. IMO, the beauty of Syncthing is that it is written in Go. Here is a note on how I use Syncthing to synchronize files with a VPS as an intermediate node. Since I already have a VPS (Digital Ocean) running, I could use it as an intermediate node to sync files between my work laptop and my PC. That would complicate the process of synchronizing files between my work laptop and my home desktop PC. Specific to my use case, however, most of the time I do not open my work laptop at home. For example, I work on my desktop PC at home and my Asus Zenbook at work, and both are connected to the internet, Syncthing can be used to sync files between those two computers. Since it works as a peer-to-peer (P2P) system, it should work well with 2 computers that can connect to each other without a central server. Its job is one and only one: sync those damn files across computers. I was not sure if Syncthing could fit my use case because the notion of peer-to-peer sync was a little alien to me, as opposed to file synchronization with central server system, as offered by NextCloud, Seafile, etc.Īfter taming my skepticism by reading more what Syncthing offers and how people use it, I was convinced that Syncthing could fit my use case pretty well. At first, I was skeptical of the idea of peer-to-peer file synchronization.
0 Comments
Leave a Reply. |