This +1 because just an upvote didn't feel strong enough

Personally I would recommend Proxmox. It's a debian based distro for hosting containers and virtual machines

Why is that, if I may ask? I've used both for years and personally I find Ubuntu has fewer footguns for a new user, and an easisr upgrade process.

Whille I agree, when it comes to the Ubuntu Desktop, their Server OS has been a stable, reliable and well supported system for me.

Thanks, glad you liked it.

Yeah, I know that the images are borked. But it's pretty late here and I was too lazy to fix it. I'll fix it tomorrow.

As someone who manages a mail server, new debian releases have the same effect.

If you want to avoid this, use a rolling release distro.

I think you are conflating desktop Ubuntu with Ubuntu Server. On a server, you absolutly want a stable, long supported LTS version.

I've been hosting on Ubuntu Server for over 10 years now, and at no point were any packages required to keep it up to date and running outdated.

That makes me very odd, I started with mandrake. Got very frustrated with the hand holding and moved to Debian, I'm not touching Ubuntu with a 10 foot clown pole.

Who in their right mind uses yaml for network config?

Whats wrong with netplan? Has worked great in my experience.

I'd say that docker is still more user friendly than podman

In the future that may change but right now podman is still green

Thanks! I am happy, if people find it helpful.

Yeah, took me a while to get the hang with Nunjucks, which I had never heard of or used before. But once I got it all properly set up, it was super simple and easy. I'll definetly write a guide to it too, eventually.

I've personally never found the need to do that. If you follow basic security guidelines and keep your server os and the docker service up-to-date, there really isn't any real threat.

Though I have heard of Authelia before and was interested in reading up on SSO, one of these days.

I have been pleased with giscus on my blog (http://roguesecurity.dev/ ) Its powered via github discussions.

Can't really help you there, since comments were never a consideration for me. They would add an unneeded amount of moderation, and potential threat, to my blog.

I see your point. But to me, self-hosting just means being responsible for the server and services and not necessarily having my own hardware server at home. And just calling it hosting is too broad a definition for me. And at the end of the day, the guide works just as well for your own hardware or a VM, as it does for a VPS.

Making the term self hosting exclusive to running stuff at home feels unnecessarily elitist. Not everyone has the space, bandwidth or family approval to run stuff at home.
You can have the term homelab if you want