this post was submitted on 30 Jun 2023
96 points (100.0% liked)
Technology
37742 readers
547 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ahh okay thanks for the explanation. The way you use it seems alot easier and concise than what I thought you used it as, specially the central home server part. Have you experienced any corruptions or loss of data using your method? That's the main concern I have with programs that sync, like syncthing.
We've been using it across many devices for several years now and haven't had any data loss or corruption. It handles 2-way conflicts very well, creating duplicate files that allow you to compare and merge when necessary.
This has only happened with our KeePass database, which is shared across all of the devices, and even then it was only when two of us modified the db within just a few minutes of each other (rare).
Wow, surprising really, might just have to try it and set it up tomorrow! Thank you, hope it works out for me lol.
No problem! Just a couple of tips...
It will create a default share upon installation; you can just delete this and create a new share for whatever/wherever you actually want it to be
Don't try to nest your shares (e.g. don't create a share in a subfolder of another share). I think Syncthing prevents this now, but in the past it would let you do it and it caused issues due to recursion.
Try to think about a logical structure of your shares that will make the most sense for your use case. If you're only syncing one folder, this won't be an issue, but if you have lots of clients with various shares, you'll need to consider how those folders are structured on the devices so that they don't overlap.
If you have any questions, feel free to shoot me a msg or post to one of the selfhosted communities. Good luck!