this post was submitted on 20 May 2026
59 points (100.0% liked)
Selfhosted
60320 readers
476 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
@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
@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.
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?)