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.
-
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. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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 use tailscale for my non-tech family.
I run a rPi with tailscale, pihole and nginx on it in their house. They connect to the their WiFi, get adblocking for free. They go to "http://homarr.sever/" pihole captures the request, sends it to nginx which reverse proxies to a homarr LXC on my server. From there they can click links to the services which are at "https://service/######.xyz". Again, pihole captures the request, sends it to nginx which reverse proxies it over Tailscale to the appropriate LXC.
One poor soul runs a mini pc with 2 mirrored ssds attached, it runs everything above plus Syncthing. They have the privilege of running the remote back up for the server.
For apps on their phone, I intend to set their phone up with Tailscale and then just have the app go to "http://dockge:1337/"... Just as soon as I learn to write the access controls to allow admins to access everything, users to access services, and services to access nothing. I just looked and there's a gui now so I could maybe do it this winter.
Bookmarked this to try this setup next weekend!
Honestly, I wouldn't.
I only run it this way because a VPS had 0 WAF, and I'm terrified of opening ports. VPS is the well trodden ground, there's tonnes of guides. Mine's a hack job borne of necessity, it works though, and I am proud of what I cobbled together.
It was my first time solving my own problems. I had my meager skill set, a basic idea of what I wanted, some vague notion of how I was going to achieve it, and a thick forehead to smash against the problem till it gave way for me.
I am going to keep running it this way though. To access my server you need to HAVE a relay rPi, and you need to KNOW a password. That's two authentication factors right there, just built in.