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
https://esc.sh/projects/devops-from-scratch/ is a good resource. Most questions you have (that are more specific) are easily searchable on the internet.
Most services you probably won't need a VPS to do, but off the top of my head a couple services which would be better hosted (not saying self-hosting them on your own hardware is bad) would be services which proxy a service. Example SearxNG, Invidious, Proxitok, etc. This is so that traffic can be shared among multiple users, and not linked back to your home IP.
What's the consensus on Cloudflare tunneling?
It’s pretty good. I understand and somewhat agree with the concerns about concentrating the web around one company, but tunnels is simply a great product. So convenient for running services behind CGNAT or dynamic IP without good port forwarding options, and it’s just set and forget. If there was an alternative that good I’d use it.
I've been using it too, it's really good and largely transparent. Of course, you can only expose HTTP traffic and you can't use your own certificates unless you pay (so *.*.domain.tld domains or deeper are a no go on the free plan), but for just normal self hosting it's the perfect solution.
I think for most people it becomes a trade off decision. Do you want to expose ports and potentially open your home to attacks but keep all traffic privately encrypted (if using SSL) and yours? Or do I keep my home unexposed but delegate trust and traffic flow to Cloudflare essentially and potentially allowing them to see my traffic?
For me it depends on the service. Nothing too sensitive or personal or already publicly available? Then Cloudflare tunnel coupled with Nginx Proxy Manager.
Highly sensitive and personal? Then do I really need to expose it to the internet? Most of the time it’s no or a VPN can be used to access those resources.
Something in between? I’d consider forwarding ports and use Nginx Proxy Manager for SSL.
For some people, exposing or forwarding ports isn’t even an option due to ISPs CGNATs, not allowed, etc. In those cases Cloudflare shines and it’s the most feasible solution.
My 0.02 cents
Hypothetically, let's say you've got a subscription to NordVPN for several months and don't want to cancel it because you're super cheap. Also, let's say (hypothetically) you're looking into self hosting ALL of your stuff for remote devices when you're out of town. How would you do it?
I was converting an old XP computer into a server, but have only done preliminary research.
Thanks, however while there are some rough notes in the Github link, it looks like this is primarily a series of videos? I was asking for text resources as I prefer those for a variety of reasons, and in this specific case it's because it's much easier to copy over any referenced scripts and clearly read commands mentioned.