You over estimate my competence. I do intend to leave my ISP firewall up and intact, but I could build layers behind it.
I run everything on a minipc (beelink eq12), which I intend to age into a network box (router, dns, firewall) when I outgrow it as a server. It'll be a couple years and few more users yet though.
I don't think I'm ever opening up anything to the internet. It's scary out there.
I don't trust my competence, and if I did, I dont trust my attention to detail. That's why I outsource my security: pihole+firebog for links, ISP for my firewall, and Tailscale for tunnels. I'm not claiming any of them are the best, but they're all better than me.
The poor are getting poorer, the rich are getting richer. Somehow, the rich have convinced some of the poor, that the reason they're getting poorer is because of the other poors (who are also getting poorer).
You should see what people did to fascists in the 1940s.
"The party cannot fail, only be failed" but unironically?
That was my conclusion as well, however I am at work and it's not appropriate to be reading docker documentation. Thank you for the write up.
I am not the person to be asking, I am no docker expert. It's is my understanding depends_on: defines starting order. Once a service is started, it's started. If it has an internal check for "healthy" I believe watchtower will restart unhealthy containers.
This is blind leading the blind though, I would check the documentation if using watchtower. We should both go read the "depends on" documents as we both use it.
Me when I'm attracted to feminine, no matter the source.
It's Watchtower that I had problems with because of what you described. Watchtower will drop your microservice, say a database, to update it and then not reset the things that are dependent on it. It can be great just not in the ham fisted way I used it. So instead I'm going to update the stack together, everything drops, updates, and comes back up in the correct order
Uptime Kuma can alert you when a service goes down. I am constantly in my Homarr homepage that tells me if it can't ping a service, then I go investigating.
I get that it's scary, and after my Watchtower trauma I was hesitant to go automatic too. But, I'm managing 5 machines now, and scaling by getting more so I have to think about scale.
I've encountered that before with Watchtower updating parts of a serrvice and breaking the whole stack. But automating a stack update, as opposed to a service update, should mitigate all of that. I'll include a system prune in the script.
Most of my stacks are stable so aside from breaking changes I should be fine. If I hit a breaking change, I keep backups, I'll rebuild and update manually. I think that'll be a net time save over all.
I keep two docker lxcs, one for arrs and one for everything else. I might make a third lxc for things that currently require manual updates. Immich is my only one currently.
"#MeToo crisis" is a strange way of putting "sexual assaulters experiencing any consequences at all". Like it's blaming the people saying #metoo instead of the sex pests and the system that allowed the sexpestery
Turns out game theory [as described in this election] doesn't describe how people (on aggregate) actually behave. It does describe how some people think people should behave (I may sometimes agree), but not how they actually do.
If I know you rationally follow game theory [as described], I'm going to offer you far less than anyone else because I know game theorists [as...] take any win, no matter how small. Ultimatum game? I offer everyone a 50-50 split, except game theorists, to whom I offer a penny. They'll take it too.
Dems didn't appeal to how people actually act, and so you all lost. Their supporters refused to acknowledge the reality of how groups behave, and so you all lost. ["you" means all of America - added for the misunderstanding]