Testing Syncthing
Reading time: 2 minutes (331 words)Author: @pugmiester
Tags: selfhosted , localhosted
Continuing on my quest to self host all the things, I’m testing an application called Syncthing. I’m sure you’re all already aware of Syncthing so I’m not going to provide too much detail here, just a few notes on my basic setup.
At the moment I’m testing the tool by synchronising my Logseq graph. My current process uses Google Drive to sync between my phone and my work laptop, where I find myself adding most of my daily notes as I work. The Google drive sync tool was already installed before I lost local admin rights (like most regular staff, a good security precaution).
I’ve installed Syncthing on my phone and my Ubuntu MacBook (it’s a 2008 model so no chance of running any modern Mac OS) and it was working happily. I added in a new LXC on my Proxmox host as a permanently available sync client. I’ve disabled all the NAT and global discovery options as my clients are either at home or running Wireguard so no need to make things available publically.
I’ve since added a client to my Chromebook, using the Linux developer mode. It’s set to also sync with my home server and seems to be doing a pretty decent job. Plus it’s fast, really fast. My Google Drive sync runs roughly every hour (a limitation of the sync tool I’m using on my phone) but with Syncthing it just appears as soon as I hit save which is pretty amazing.
I’ll be doing lots more testing over the coming days / weeks but it’s looking like a really solid option for replacing something like the Google Drive sync tools, removing another cloud from the process. At some point, when I get the hang of things, I’ll setup a proper sync server with a crap ton (the technical term) of storage and look at testing photo sync but for now I’m just going to see how it handles the small stuff and take it from there.