[locknitpicker]

> It's like someone should make a file... maybe in /etc ... and put short names for services in it... maybe it could be called /etc/services...

People shit-talk container orchestration systems like Kubernetes, but if anything they greatly simplified (if not completely eliminated) the need for this sort of network bookkeeping.

[nesarkvechnep]

You forgot the /s at the end.

[adestefan]

All our bookkeeping is now in YAML. Watch the spaces on your way out the door.

[data-ottawa]

Learning nixos had been a lot of fun for me.

Your comment unironically is something I prefer and one of my biggest pain points with Linux.

As a newb, I'm sure there's something called with a mycommonproblemd name that has a stateful interface. But sometimes that all adds up to make things feel complex. And it let's me make stupid mistakes, like I forgot to close or open a port on firewalld, or I disabled a container but forgot to commit a change to my systemd units.

It's nice to just have a nice file called myservice.nix that tracks the firewall port, name, systemd startup and update scripts.

[sgarland]

And don’t forget to quote your port assignments and version strings.

[pirates]

Hacker News loves to make snarky comments about everything to do with K8s and YAML all the time, and yet in my experience the amount of times an issue was caused by actual YAML can be counted on one hand.

Way more often it’s developers who can’t figure out that their http library only supports 2 concurrent connections, or emit garbage/malformed log lines and then bitch that they can’t see their app logs because we dropped them, or can’t be fucked to do “kubectl describe” in their own developer namespace that they have full permission for.

If you truly experience issues with just using YAML then you need to skill up probably.

[SAI_Peregrinus]

Most of the issues with YAML are really issues with people who think that since "configuration as code" is good, that "code as configuration" must also be good.