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.
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
Off topic but could you explain a little on how you use a VPS to access your internal services? There’s a few services I want to open up but I don’t trust cloudflare and I don’t want to port forward.
Not the OP, but my current solution involves a small instance in AWS with a wireguard server in docker. This is configured with a few peers. One peer is a container on my home server that can access my jellyfin deployment. This container is also running socat to redirect the traffic to jellyfin. Then my phone and laptop are the other peers and I have a DNS record pointed to the IP of the wireguard peer on the server, if that makes sense.
I've been using this image pretty painlessly. The only hiccup I had with setup was ensuring persistent keep alive was configured on the peer forwarding traffic to jellyfin.