Empathy [he/him]

I want to add that, like you, I’ve become a big fan of restricting the numbers of ways to do something.

IMO, It’s more time wasted choosing, more time wasted reviewing, and makes it easier to overlook errors. I want more opinionated languages and frameworks.

I kept seeing so many different ones recommended and I kept getting weird issues I didn’t understand with most of them. I don’t often need to make a bootable Linux USB, but every time, Rufus did the job quick and easy.

Disclaimer: I don’t know much about securing the container itself. The considerations I discuss here are mostly networking.

What I’ve personally been doing is using k3s with Cloudflare Tunnel (routed using DNS like in this documentation) as an ingress.

With Cloudflare Tunnel, if you create an application in front of it, you can require authentication and add a list of allowed emails.

I could replace k3s with a different Kubernetes distribution, and/or replace Cloudflare Tunnel with a different ingress (e.g., Tailscale Funnel or more common ingresses like nginx).

Great to know this was a bug. It felt a tad immersion breaking for every origin character to be so interested all of a sudden.

I love both proprietary software and open source software, and personally I kinda like this warning.

How much of a concern it is for software’s code to be proprietary, is probably personal opinion. For this reason, maybe yellow is a bit too much? I think making these errors grayscale might be a good middle ground.