Selfhosted
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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
view the rest of the comments
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?)