Quite literally my first thought. Great, but I can’t issue certs against that.

One of the major reasons I have a domain name is so that I can issue certs that just work against any and all devices. For resources on my network. Home or work, some thing.

To folks recommending a private CA, that’s a quick way to some serious frustration. For some arguably good reasons. On some devices I could easily add a CA to, others are annoying or downright bullshit, and yet others are pretty much impossible. Then that last set that’s the most persnickety, guests, where it’d be downright rude!

Being able to issue public certs is easily is great! I don’t use .local much because if it’s worth naming, it’s worth securing.

If you look deeper at the recorded PR commit, comments, and package description it’s clearly straight up mean-spirited.

I have two words for you, “compensating controls.”

It’s like goddamn magic.

Is it bad my third thought after “🥰” and “unrequited love 😢” was immediately “oh gods I hope it doesn’t start marking the porch”?

Virtualization in general? Sure, I can. I’ve tried it a bit with bhyve. But it’s definitely a lot heavier since I’m now running a full Linux os and dedicating resources to it to run docker just to run a python or node app.

Learning the project is in Go though is a sigh of relief. Professionally I’ve moved to Go (from Python) just because it’s so damn easy to build and distribute.

I just wish there was better support for the other *nix’s. While the language support them just fine, docker on the other hand strangles it. =(

For me it’s more like new interesting self hosted project and then find out it’s only distributed as a docker container without any proper packaging. As someone who runs FreeBSD, this is a frustration I’ve run into with quite a number of projects.

The Gays would kindly ask this list include the HIV crises.

Thank you!