The fourth article in my series about “self-hosting for newbies” explaining how I take care of backups for my YunoHost server.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters DNS Domain Name Service/System FAA Federal Aviation Administration IP Internet Protocol SSL Secure Sockets Layer, for transparent encryption VPS Virtual Private Server (opposed to shared hosting)
[Thread #103 for this comm, first seen 18th Feb 2026, 19:21] [FAQ] [Full list] [Contact] [Source code]
I don’t get the resentment for yuno. In the end it is a hobby. You can have fun building everything from scratch. And you can have fun, using pre configured services.
What counts is that you get away from big corp.
Can’t say much about your tutorial though. Didn’t read it. I’m sorry. ;)
Tough crowd. I used Yunohost back in the day. I thought it was pretty good. Great for someone who is just starting out. It has evolved, and I think the newest version boasts the largest app catalog in it’s class.
In part one, I explained why I’m passionate about self-hosting and I discussed what you need to get started on this journey (a VPS and a domain name)
You didn’t need either of those things. This reads like an ad for yunohost.
I have used (and loved) Yunohost for a long time, and I host it at home. A few years back, I did set up a vps to proxy the traffic (over wireguard) so that I could actually get a letsencrypt cert. Some apps really don’t like self-signed certs.
You do not need a VPS, proxy, or wireguard for letsencrypt.
You are right, you don’t need yunohost, but it makes selfhosting pretty easy.
send from my piefed instance hosted by yunohost ^^
No, it’s legit. Elena has been tooting and peertubing about the fedi and her self hosting journey for over a year.
It still reads like an ad for yunohost…
I think one of the mistakes many newb self hosters make is thinking of systems in their entirety rather than as components.
“How to install pihole on a raspberry pi” and “how to setup nextcloud on yunohost” are examples. All using very specific tools and very specific steps.
I’m noticing this more and more with documentation for apps where they tell me to use their specific docker-compose file and have instructions to use let’s encrypt in a specific way rather than referring you to let’s encrypt as an option and pointing you at their docs.
People aren’t learning how to use each of these tools and how to be flexible in their implementation.
As someone who has never done any serious coding work or collaboration, hadn’t touched Linux in 18+ years and am really only fluent in windows and Mac, and with limited time to get up to speed, I fucking love opinionated guides.
Tell me exactly what to do to get it up and running. Let me learn along the way, but don’t expect me to be able to read and understand the pros and cons of lets encrypt vs other solutions.
I simply do not have the requisite base knowledge to make informed decisions on this.
If you wanna leave it up to me how to do a golden gate assembly, quick change reaction, or a gibson assembly, I can handle that.
Understanding the nuance of docker networking, reverse DNS,maintaining SSL, and just generally how to make it so I can use a hostname and not an IP address to access my services locally is something I want to learn. Eventually.
It’s not that your critiques of guides are invalid, but they may just not be structured for general learning. And their target audience is temporarily ignorant fools like myself.
