|
|
|
|
|
by caconym_
15 days ago
|
|
I run Syncthing in a hub-and-spoke topology where the hub is a headless VM with a volume hosted on my NAS. This is half for my sanity wrt remembering what's peered with what, and half because it works much more consistently across network boundaries. The way I use it, it's a 1:1 replacement for the way I used Dropbox: a directory of files that are continuously synced across different machines, with a durable central copy that gets regular snapshotted backups. I understand that Dropbox has more features now, but that's pretty much all it was when I started using it; and the fact that Syncthing supports other use cases than mine doesn't mean it isn't a perfect fit for mine. Out of all my experience self-hosting ~replacements for consumer cloud services, it's probably been the most successful by far. |
|