Speak for yourself, some of us use our homelabs to serve ourselves as customers because we refuse to pay for nickel and dime services that exist for the sake of convenience.
I realize that homelab goes a bit beyond localhost, but we all start somewhere.
And that's fine. But it is not at all required for self-hosting things. Maybe you do that to improve your skills for making money. Maybe you do it because you just enjoy all the complexity and learning the systems. All legit, but completely un-needed obstacles for people that just want to learn how to, or just accomplish, self-hosting.
It's like writing a page on how to make bread at home but then spending most of the words on how to build an transient extra-oven outside with special parts instead of just using your oven and talking about the actual recipe steps.
And that's fine. But it is not at all required for self-hosting things.
It's not required, but, once you have a handle on it, you get to save a lot of time and hassle. For example, I just checked my old docs for installing and updating Nextcloud. It's 17 printed pages. My new docs are:
Personally, I run that nightly because, like someone said in another comment, "so what if your homelab is down for a day." For me having a day of downtime wouldn't be the end of the world, so everything's homogenous and auto-updated. I only touch it when I need to update to new major versions.
In my experience I spend less time fixing issues related to containers than I used to maintaining everything by hand.
Comments
Speak for yourself, some of us use our homelabs to serve ourselves as customers because we refuse to pay for nickel and dime services that exist for the sake of convenience.
I realize that homelab goes a bit beyond localhost, but we all start somewhere.
And that's fine. But it is not at all required for self-hosting things. Maybe you do that to improve your skills for making money. Maybe you do it because you just enjoy all the complexity and learning the systems. All legit, but completely un-needed obstacles for people that just want to learn how to, or just accomplish, self-hosting.
It's like writing a page on how to make bread at home but then spending most of the words on how to build an transient extra-oven outside with special parts instead of just using your oven and talking about the actual recipe steps.
It's not required, but, once you have a handle on it, you get to save a lot of time and hassle. For example, I just checked my old docs for installing and updating Nextcloud. It's 17 printed pages. My new docs are:
Personally, I run that nightly because, like someone said in another comment, "so what if your homelab is down for a day." For me having a day of downtime wouldn't be the end of the world, so everything's homogenous and auto-updated. I only touch it when I need to update to new major versions.In my experience I spend less time fixing issues related to containers than I used to maintaining everything by hand.
You've missed his point, he's just saying you don't need to use docker, just set it up normally. Or what was normal 10 years ago anyway.
Docker _is_ normal these days.