While democracy burns, democrats do absolute dick.

Why do like, houses have doors man. You gotta eliminate all points of egress for security, maaaan. /s

There’s no particular reason to disable root, and with a hardened system, it’s not even a problem you need to worry about…

There’s no real advantage to disable the root user, and I really don’t recommend it. You can disable SSH root login, and as long as you ensure root has a secure password that’s different than your own account your system is just as safe with the added advantage of having the root account incase something happens.

You can’t really disable the root user. You can make it so they can’t login remotely, which is highly suggested.

AI for form processing and/or paperwork would be great if done right.

Immagine you submit an application and either it’s verified almost immediately, or is elevated to a real person because there’s an issue. Could be awesome.

Correct. If space is such a big problem for you that it’s unconscionable to use a 4U mini rack (which again, like what the fuck), then mounting hardware on the wall is a completely valid option. It’ll take up zero floor space.

Only full size racks. You don’t need to buy a full size rack. You can get very small racks these days that are smaller than a little chest cooler. And why are you under the impression that you have to mount it on the wall?

I’m coming to appreciate Hyper-V more and more to be honest. It’s a very mature virtualization environment. The only issue I have with it is the inability to do GPU-passthrough. Once they figure that one out, I probably won’t bother with anything else.

Because developers use cross-compilable languages to pump out Windows executables without knowing or understanding or caring about the Windows environment. I mean, ~/.whatever still works under Windows.

Docker is so bad. I don’t think a lot of you young bloods understand that. The system is so incredibly fragmented. Tools like Portainer are great, but they’re a super pain in the ass to use with tools/software that include a dockerfile vs a compose file. There’s no interoperability between the two which makes it insurmountably time-consuming and stupid to deal with certain projects because they’re made for a specific build environment which is just antithetical to good computing.

Like right now, I have Portainer up. I want to test out Coolify. I check out templates? Damn, not there. Now I gotta add my own template manually. Ok, cool. Half way done. Oops. It expects a docker-compose.yml. The Coolify repository only has a Dockerfile. Damn, now I have to make a custom template. Oh well, not a big deal. Plop in the Dockerfile from the repository, and click “deploy.” OOPS! ERROR: “failed to deploy a stack: service “soketi” has neither an image nor a build context specified: invalid compose project.” Well fuck… Ok, whatever. Not the biggest of deals. Let me search for an image of “soketi” using dockerhub. Well fuck. There are 3 images which haven’t been updated in several years. Awesome. Which one do I need? The echo-server? The network-watcher? PWS?

Like, do you see the issue here? There’s nothing about docker that’s straightforward at all. It fails in so many aspects it’s insane that its so popular.

This is why rack mounts were made. Hell, I’ve seen a lot of custom builds where people have mapped out the server on their wall and it takes up no floor space. Something like this: https://i.xno.dev/kG9Wx.jpg