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
This multi-server front project, Jellyswarrm is really interesting, which allows the Jellyfin clients to access more than one Jellyfin server simultaneously. I think it may do what you want when combined with server sync.
Would definitely test extensively before putting in production, hehe.
It doesn't really solve my use-case, since we do a combination of direct stream when possible, as well as local sync/cache but only for transcoding purposes. As well as local users only, with the federated sharing taking care of permissions, so that we don't transfer user information between eachother.
Jellyswarrm is certainly a lot closer than other solutions people have suggested though.