That makes sense to me… You really only want one path for the air flow. E g. In through the front, over the components, and out the back.

Most of the fans in this setup are just fighting against each other.

My sister is a civil engineer in PA and is familiar with this situation. She told me that basically these municipalities did not take care of their pipes, refused to raise any money for them, then, when they got old enough that the situation became critical, sold it off. Now this company comes along, has to make required fixes to the pipes, and has to raise the money to do so. The private company gets to be the bad guy, while the local governments, who neglected the pipes for a decade or more, don’t get heat.

All this said, if they weren’t allowed to sell it to a private company, there would be no “get out of jail free” card and maybe they would have pushed harder to take care of them damn pipes.

Point is, I don’t think it’s quite as simple as it looks on the surface.

js’s JSON.stringify(obj, null, 2);

That could be avoided by using on prem properly, too. People are very capable of making bad infrastructure whether on prem or cloud.

I used to like bootstrap. Still do. But it has some faults… Depending on your needs you’re loading a lot of CSS you aren’t using.

Bootstrap 5.3 is 59kb before gzip. 6700 lines of code. That’s a lot to just apply some simple styles.

There are a ton of lighter weight alternatives nowadays.

Client <-> vps <-> home server

I’m looking to set up exactly this for myself with a linode vps, and wireguard containers. Any tips? Even a docker compose snippet would be helpful.