Pretty typical. Apple has been doing this for a long time now.

Yeah, that’s how just about everything in security goes. I find policyd to be far more annoying.

Because apparently people are stuck in the mindset of about 10 years ago when people used to get tripped up over it. SELinux is rarely ever a problem for anything these days. This post is dumb.

They stopped saying that a long time ago. It became something like 2x ram until beyond 4GB then it was something more sane.

I switched from Portainer to Komodo a while back. I like how everything is declarative. It almost has a Argo CD feel to it without needed kubernetes.

The $1 is a positional variable. So if you run ./script.sh arg1 $1 would be arg1 in that example, $0 would be the ./script.sh. It’s the simplest way to pass an argument to a script.

Finally? It’s been SUSE’s default for at least a decade now. It’s the default for Fedora since 33, so ~5 years ago. Btrfs has been working for a long time.

Use a modern filesystem like btrfs or even lvm with thin provisioning to solve that problem. Separate partitions for ease of backup, but they all pull from the same pool of storage.

I was that guy. And then ended up with that career partly because of it.

You manually run that instead of letting it automatically stage updates in the background?

Yeah, but if you were doing lxc + docker per container you might as well use this oci as lxc method. I think both methods are silly, but that’s just my opinion.

How does that make it easier for maintenance?

You have each “docker” container in there own lxc running docker? That’s a silly way to do it if I’m understanding correctly. You’re adding overhead to containers for little to no benefit. You could put them all in the same lxc or Proxmox supports OCI containers natively now.

Sure. Red Hat moved CentOS where it belonged, upstream, in between Fedora and RHEL. That generally upset people who wanted a bug for bug free version of RHEL. Rocky and Alma were both born out of that era. Alma actually works with Red Hat, created its own SIGs and contributes upstream to Fedora. Rocky on the other hand is backed by CIQ. Does not contribute anything upstream, bends/breaks licensing to get source from Red Hat to get as close as they can to that bug for bug code without doing any engineering themselves. Then CIQ poaches Red Hat employees and customers by offering way cheaper support because they don’t pay for any of that pesky engineering.

Honestly at home there really isn’t a reason not to just use CentOS Stream imo. It is ABI compatible with RHEL. There is a misconception that it is a “rolling distro” but it only rolls through minor releases in that it doesn’t even have minor releases. Alma is something in the middle. Actively contributing, ABI compatible, and offers minor versions.

Hell, even Oracle at least adds their own twist to OEL instead of straight up ripping off RHEL.

At least use Alma. Rocky is toxic to the ecosystem while Alma contributes to the ecosystem.

Do you not understand what a suite of tools is? It’s a curated collection of tools that have been chosen to work together. You’re describing the reasons why Pangolin is in fact a full suite. You’re right, Pangolin is the bit that orchestrates them and brings them together with an easier way to manage them. That’s what a suite of tools does.

Pangolin uses gerbil with newt for those wireguard tunnels. That’s a massive improvement already. It also adds a bunch more features like vpn, you can crowdsec, and more that I don’t use. To say it’s debatable if it’s a suite of tools is just wrong.

I’ve set it up next to my NPM and it’s more complicated, but so much more capable. Traefik is what it uses to proxy things. You’re comparing a full suite of tools with just one piece.

Free vps in oracle cloud with Pangolin. Never have to worry about explaining VPNs.

I think that’s why it launches with the app menu open by default.