That’s what aliases / functions in .bashrc (or whatever shell you use) are for. You don’t need to always write the full code.

EDIT: Looks like .bashrc hurt you guys.

This website is deprecated.

It’s kept around mainly for historical reasons.

I’ve tried Docker Swarm because Kubernetes seemed like an overkill for a cluster of 4 small-ish servers. There have been several issues (networking for example) that took me two days to solve - by reinstalling the machine completely.

There are some hoops and hurdles along the way, some command will just literally brick your cluster without any notice whatsoever (like removing the second manager, leaving only one and cluster stops responding, but you get no warning that’s gonna happen).

Also secrets, where there is no simple way to manage them, or replace them. You can’t just replace a secret, you have to remove and recreate it. Which means turning off the service or creating a new secret with a different name and do a rolling update, which is just annoying to do every time unless you can afford a robust CI CD pipeline code that does it automatically.

Ooooh, I just checked and I am indeed not running the AIO. Must be a new thing, and I though I had it because I didn’t set up much, but I really just used a premare docker-compose.yml, which is why I didn’t remember any advanced setup. It still uses multiple containers.

I stand corrected.

What do you mean no internal IP? I can access the instance on my local network via RPI address no problem.

EDIT: Realized I didn’t use AIO. Sorry.

Probably because it’s easier to fuck up. With piping to xargs, you are forced to put the delete command last.

Theoretically, any registrar can hijack your domain.