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
It's a huge problem that so many people act like it's super easy and simple. It's incredibly complicated to someone who is not a networking professional.
When I was starting out with selfhosting and stuff, I had tons of issues with networking, reverse proxies, etc. And much of the advice here was not... particularly helpful. I genuinely don't think most people here understand how much they know, and how much comes across as gibberish when they speak to a true newbie. I still see it in this forum all the time for new people. Just the other day someone described themselves as a total newbie, nothing more than Jellyfin running on a Mac locally, and a comment I saw suggested their next step should be running proxmox and setting up VMs and this that and the other service. Like... that's not a good next step.
When I was given a similar suggestion, I asked why I would need proxmox for my project, and I was told something along the lines of, "Don't discount their usefulness if you're trying to do this as a career." I am not trying to do this as a career. I already have one of those. I'm trying to replace subscription services with something more economical and under my control.
That's it, exactly.
This has been my experience with self-hosting too. There are so many different areas of concepts that need to form a cohesive whole. Following a how-to and pasting some commands can lead to something running, but then there are worlds of knowledge to actually understand it. Especially when complexity seems to increase exponentially.
Funny thing is that for every low-level concept I actually learn, the more I appreciate my OpenBSD computer that I mostly play around with otherwise.
@artyom I think part of it is that it *is* easy.... when you're working on your own setup, that you built, and know all the components of, and know all the long term goals of, that was built over years piece-at-a-time...
Get anyone who acts like it's easy to work on someone's setup that isn't their own, and they'll quickly remember how complicated it all is.
I would agree with this and the sentiments above. If I am on my system, I know how I have it set up. I can reference pages of notes if I do forget how I did something. I am more familiar with my server and services. When it comes to someone else's set up, I can tell you how I did it, and that it works for me. You've got to kind of adapt it to your scenario. I can understand how that would be frustrating for someone starting out, as with Linux, there seems to be a thousand ways to do one thing.
It has nothing to do with whose setup it is and everything to do with an immense amount of specialized knowledge that requires, at the very least, months to even begin to understand to the extent that you can deploy your own server.