As someone who’s set up and managed critical business applications I would say that it’s perfectly fine to host your own provided you have decent hardware that’s capable of doing what you need and as a dedicated business line to provide connection.

If you try to run mission critical business applications on a home internet connection you’re going to have a really bad fucking time. But hosting business critical applications on appropriate hardware and a 1Gb/s business connection with an SLA is going to meet 95-98%% of all business applications.

If something like that sounds expensive or too difficult to do then it’s too expensive or too difficult for you to host yourself. Just go with a provider and sidestep self-host.

Debian, baby.

Chest freezers are exceptionally energy efficient. It’s not a very good comparison.

I really love home labs but this sounds incredibly over engineered for its purpose… I would expect a set up like this for an enterprise environment…

I very highly recommend that you take the time and just switch. Caddy is simply fabulous. It’s designed to work (assuming it’s compiled with the module) with containers and use docker networks for routing. It makes it easy to spin up containers and directly reference the container names instead of remembering IP addresses and particularly comes in handy when your entire environment is containerized.

You can pull the caddy image and run it in docker and as long as your environment is configured correctly you can simply reverse_proxy @container and you’re done. Caddy pulls all the relevant port information directly from the container API.

I get such a nerd boner thinking about it.

Lineage is built directly from AOSP images, so this makes perfect sense.

It’s an android system component. You allowing unattended updates, or clicking “update” is the consensent.

Stop being disingenuous.