Self Hosting 101 – A Beginner's Guide
ente.io
ente.io
Basically some mid-spec box that comes preinstalled with some nice web UI that lets you easily install popular self-hosted applications (immich, nextcloud, jellyfin, wireguard, etc..).
Ideally it'd let you host an at-home iCloud without having to go through the headache. A lot of people I know (including hobbyists & swes) don't self host because setting up a linux vm/box and configuring everything + maintenance would take too much time.
I think the biggest weakness with this is HA. Residential internet/power isn't the most reliable and even though my homelab server is up ~98% of the time, the 2% is VERY annoying and always happens at the worst times.
Security would also be another large concern. I'd imagine a bad actor would have a harder time getting into my iCloud/Google Photos than my immich server.
You can self-host Umbrel on your own hardware[2]. I'm not sure if they allow for multiple nodes to stay in sync. If (/once) they do, it'd solve for disasters / availability as well.
[1]: https://umbrel.com
This lets you host the most popular self hosted apps with a click[2] and you get an IP from us. :-)
After a few months of it working without a hitch, I killed my dropbox subscription. Now I pay a few pennies for my NAS a month, and $3/mo for backblaze.
I'm suprised at how many of my homelab friends don't maintain proper backups.
In that sense, I guess we aren't as far off from the SMBs that don't have backups in place, although if you ask the homelab people about it the answer is usually "I can live without most of this if it gets lost".
I'd imagine 90% of homelab storage is movie/tv show 'backups' and aren't that sensitive
https://www.synology.com/en-uk/dsm/feature/docker
I struggle with the difference between "lab" and "production". You may start messing around with Home Assistant on a Raspberry Pi but when your partner can't turn on the lights with a voice command you're going to find that you need something more resiliant.
For friends and family unraid is nice because it has a much bigger repertoire of "Apps" (mostly docker containers with some minimal UI integration). It demands a lot more from the user than Synology and looks a lot scarier, but there are no difficulty spikes. Once somebody knows how to use it it's pretty smooth sailing without having to learn anything new.
Or you can go one step further and just go with a managed solution. For example Hetzner has a managed NextCloud, then you don't even have to worry about updating that.
And my advice to someone considering to start self hosting: Start with a setup that consumes less power and once you have the 80% the idea of the services you want to keep running 24x7 then you scale up your server or build/buy a new one.
Honestly, I got similar feedback when I got this reviewed internally. At this point I am not sure how to write so that it doesn't seem LLM generated.
Would be helpful if you could share why you thought this was LLM generated. The suggestions I have gotten so far has been to remove bullet points and sections - which I feel breaks readability.
That's just my take, again I don't think it's that bad. The article would be a useful breakdown for beginners.
(Also, I'm sure you know, LLM content sounds that way because the LLM was trained on content just like this, so it's not really surprising that a guide generated by an LLM would sound like the kind of guide that was used to train an LLM...)
- h2 titles feel as basic as possible, just "what self-hosting, who self-hosting, why self-hosting, ..."
- SEO spam often overuses keywords; on this page, it feels like "self-hosting" is used a bit too often, even if it's well-intentioned
- the text ends in a classic LLM warning "remember to be careful"
- predictable sentence patterns
Some of these things are good for readability. I guess this article feels a bit too plain? I think tech company blog posts add a unique style and voice these days, because otherwise they'll blend in with the average SEO/LLM content.
Also editing nits:
> self hosing
> Self Hosting
> atleast
Good self-hosting tips, though. Thanks for sharing.The overuse of "Self Hosting" is fair. Better H2 titles would have made it less frequent. Will be more thoughtful about this the next time.
The unique style and voice is where I am struggling with. Have always been instructed to write in a plain tone and simple English so that its easier to read through.
But when I got to "How to Start Self-Hosting?", which is the section I was most interested in, I got a strong sense of déjà vu.
Reading this section felt exactly like I feel when I hit a bad prompt on ChatGPT. I feel I'm being given a huge dump of keywords but nothing that lets me make any progress. Reading it I felt the same frustration I do with ChatGPT as I have to prompt it again with "Can you elaborate on bullet point 6" to get anything useful out of it.
With ChatGPT the reason is usually a prompt that was either too broad/open-ended or a difficult topic for ChatGPT to answer. And it has a tight limit on how long the answer can be, which is understandable. For an article though it feels a bit jarring and there is no immediate way to ask for details.
I think the rest of the article is fine really. Sure the word of caution is exactly what LLMs do but unlike LLMs, which usually state the obvious, it has a lot of useful information.
1- Always longer than necessary with a lot of fluff
2- Favor lists and hierarchy
Because they're trained on mostly SEO spam and buzzfeed-style articlesI asked Gemini to "write an article about self hosting" and the output structure and content is eerily similar
Here is a side by side comparison: https://i.postimg.cc/kXXpWgnZ/why-it-look-like-LLM-generated...
The bigger issue is if your ISP puts you behind a CGNAT in which case you’ll need a product like cloudflare tunnels or you can roll your own with a vpn tunnel and a vps with a static IP.
[1]: https://developers.cloudflare.com/api/operations/dns-records...
[2]: https://www.noip.com
Of course you can do a similar thing yourself by getting a cheap VPS somewhere (~$2/month with no-name hosters from lowendbox.com) and connecting your server to it via wireguard
Statements like this are so disingenuous:
"Monitor Your Services: Set up monitoring to keep track of your server's health and performance: Use tools like Prometheus and Grafana for detailed monitoring Set up alerts to notify you of any issues"
That reads like it'll take 5 minutes, but requires learning PromQL, spinning up multiple services, which you then also have to maintain and support, and come with all their own issues.
"Full control over files, no storage limits except hardware"
This is technically true, but for the average user, compared to the vast and free data in Google Drive is just not really valid. Then get into the issues of maintaining drive arrays for redundancy, back-ups, IO performance, etc.
Everything that says "enhanced security" but you're asking someone with no experience in self-hosting to get security right. That's a really big ask.
I don't want to keep going on dissing the article, which is a good attempt at summarizing where the industry/hobby is now. I love self-hosting things at home, I've learnt a lot, and it lets me geek out. But, I'd contend that almost every sentence in that article is flawed somehow.