The fourth article in my series about “self-hosting for newbies” explaining how I take care of backups for my YunoHost server.
The fourth article in my series about “self-hosting for newbies” explaining how I take care of backups for my YunoHost server.
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.
I don’t remember exactly why, but I couldn’t get it to work any other way. First problem was incoming port 80 blocked by my ISP.
Right? This is the whole “lack of understanding” that I’m going on about. “But the install instructions for some other application said to do this.” So it becomes cargo-cult system administration.
It’s how we end up with
curl https://some.rando.url/install.sh | sudo bash -cas an acceptable way of installing software. Don’t understand it, don’t question it, don’t look at what that shell script you’re running as root does, just copy / paste / and go! I don’t want to care about the details!And you see it in the comments in this forum where anytime anyone asks a question there are dozens of replies like “just use yunohost” or “just rebuild your entire server with unraid” without addressing the one component that needs addressing or offering multiple solutions. It’s just “my click and forget solution worked for me so it’s the way everyone should do it.”
This is how we end up with walled gardens - to protect these people from themselves. Self-hosting should involve some amount of learning about what you’re doing because “there be dragons” out there.
I have nothing against yunohost or letsencrypt (the latter is simply amazing) - but one should understand that these things are components that are part of a larger system.
</rant>