@pixeldaemon Syncthing. We have one “authoritative” fileserver running syncthing, and then a bunch of “clients” (laptops, phones) that sync up to the fileserver. This doesn’t work for, say, terabytes of movies/music, but for important stuff like photos/tax records/whatever, it means we can make changes on any “client” and it gets synced to the “server” and all the other “clients”
How do you set up syncthing with a host/client configuration?
I planned on setting it up with 5 devices but as soon as I got to 3 devices I started having issues and didn’t like the structure conceptually of “everything syncs to each other” vs having a “source of truth” with 2-way sync.
TBF my issues with syncthing were probably user error but still frustrated me enough that I bailed.
@yestalgia So I set up syncthing between a server and one client. Share folders between them. Figure out how you want the folder data replicated; for my phone pics, for example, the sync is one way from (phone) -> (syncthing server). For kids’ health stuff, it’s a two-way sync; because the sync might be (my laptop) <- (syncthing server) <- (my wife’s laptop), or vice-versa. Then add another client to the syncthing server, following the same process. Never sync client-to-client; always via server
@yestalgia I will say that the configuration is not the most intuitive. Part of it is just that the web UI is, imo, not that good. There’s a lot of confusing stuff exposed to users that isn’t really important for like 99% of use cases.
(who cares whether compression is metadata only or all data or none? wtf is “introducer” vs “auto-accept”? why do I need to see a random hash for device or folder id in addition to a device or folder name?)
@pixeldaemon Syncthing. We have one “authoritative” fileserver running syncthing, and then a bunch of “clients” (laptops, phones) that sync up to the fileserver. This doesn’t work for, say, terabytes of movies/music, but for important stuff like photos/tax records/whatever, it means we can make changes on any “client” and it gets synced to the “server” and all the other “clients”
For more traditional cloud, I recently installed copyparty (https://github.com/9001/copyparty) w/ https://github.com/romaan7/white-gold-theme-for-copyparty
How do you set up syncthing with a host/client configuration?
I planned on setting it up with 5 devices but as soon as I got to 3 devices I started having issues and didn’t like the structure conceptually of “everything syncs to each other” vs having a “source of truth” with 2-way sync.
TBF my issues with syncthing were probably user error but still frustrated me enough that I bailed.
@yestalgia So I set up syncthing between a server and one client. Share folders between them. Figure out how you want the folder data replicated; for my phone pics, for example, the sync is one way from (phone) -> (syncthing server). For kids’ health stuff, it’s a two-way sync; because the sync might be (my laptop) <- (syncthing server) <- (my wife’s laptop), or vice-versa. Then add another client to the syncthing server, following the same process. Never sync client-to-client; always via server
@yestalgia I will say that the configuration is not the most intuitive. Part of it is just that the web UI is, imo, not that good. There’s a lot of confusing stuff exposed to users that isn’t really important for like 99% of use cases.
(who cares whether compression is metadata only or all data or none? wtf is “introducer” vs “auto-accept”? why do I need to see a random hash for device or folder id in addition to a device or folder name?)
@pixeldaemon I used to use Seafile, but it is clunky and annoying, and it will also never ever be in debian due to upstream copyright sketchiness.