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
I think you're missing the point - that's neither simple nor easy for most people. I'm a network engineer and I don't wanna deal with setting up and (being responsible for troubleshooting) a bunch of VPNs! Nevermind the additional power/CPU usage from the tunnels. My parents just got fiber and they don't even have a public address (ipv4 or v6) which just adds another layer of headache. thanks west virginia...
I'd much rather deal with setting up a few VPN gateways which is trivial at most...than securing a public web service. I deal with that crap enough at work.
There are a lot less variables to contend with with a single VPN endpoint which undergoes considerably more security auditing than N public web services. Many of which I don't have the time to review myself and mitigate if they decide to suck at coding.
Edit: I share my services with less than 5 households though.
Edit2: I'm not sure what public ipv4 or ipv6 has to do with this. My remote sites use starlink ipv4. I haven't setup ipv6 on those internally at all. They all tunnel via wireguard to my homesite.
When I set up wireguard it was just more complicated when one side didn't have a public IP. Whyyyy can't we adopt ipv6 already.
also fyi starlink has public ipv6 available if you DO wan't to set it up. been hosting a minecraft server off a starlink connection lol.
At my remote site it has little value. At my home I have IPv6 setup on Starlink as my secondary backup internet. I use Fiber as the primary that has a public IPv4 and IPv6.
Could just use a VPS though I guess if you want.
If you have the skills to setup a Jellyfin server you also have the skills to setup wireguard.
That's a very specific use case.
They appear to offer a guided installation for windows users.