davad

I’m mostly a lurker. I’ve also been selfhosting for at least a decade, and I’m a professional in the IT sphere.

I wholeheartedly support this rule change. Hardware is a big part of selfhosting/home labs. And for some people, it’s a hard leap to make.

If we end up seeing lots of redundant posts (e.g. “Can I use my old laptop to host stuff?”), we can always start an FAQ or something. But until and unless it becomes a problem, keeping the rule simple sounds perfect.

In an enterprise setting, you shouldn’t trust the server firewall. You lock that down with your network equipment.

Edit: sorry, I failed to read the whole post 🤦‍♂️. I don’t have a good answer for you. When I used docker in my homelab, I exposed services using labels and a traefik container similar to this: https://docs.docker.com/guides/traefik/#using-traefik-with-docker

That doesn’t protect you from accidentally exposing ports, but it helps make it more obvious when it happens.

(another pet peeve of mine is “rest” APIs that use 200 response codes for everything)

Yup, also some APIs use GET for everything. It’s a pain. And it means that filtering by verb only helps if you’re intimately familiar with the API. And even then, only if you keep up with changes as they happen. So really, only if you’re developing the API yourself.