I leave my servers running 24/7, thats the point of a server. Also my home automation would be a little pointless if its off.
I did have a UPS, but it died and I have got round to replacing it.
Its all horses for courses, if your homelab is a playground to test things out then turning it off when not is use is fine. But some have live services that you may want at a moments notice and there for having it up all the time is better.
Hello
I would use a state change as the trigger, then in the action use an if to look for an off. That way you could use it to turn on the speakers with the chromecast
I use swarm in my home lab, I don't have any docker things at work so Kubernetes is way more then I want to manage.
All my stacks are in a git repo, I have an ansible playbook to update them if needed. I also have most things tracked on new releases (https://newreleases.io/) so I know when something needs an update, then I can either update the git repo by hand or use ansible.
Also have a look at docker contexts, you can manage your swarm from a remote location.
Depending on the login flow, I have a lot of stuff behind an oauth proxy. So that you have to have a working 2fa account to see the non 2fa system behind.
I would have a cron that runs a script to pull the list and update IPset, this might not work.
make a file on your docker server with the below in it, set the file to execute chmod +x file.sh
#!/bin/sh
ipset -q flush ipsum
ipset -q create ipsum hash:ip
for ip in $(curl --compressed https://raw.githubusercontent.com/stamparm/ipsum/master/ipsum.txt 2>/dev/null | grep -v "#" | grep -v -E "\s[1-2]$" | cut -f 1); do ipset add ipsum $ip; done
iptables -D INPUT -m set --match-set ipsum src -j DROP 2>/dev/null
iptables -I INPUT -m set --match-set ipsum src -j DROP
Then add a cron file in /etc/cron.d that runs the script every 24 hours
I use nextcloud news and app, bur did not know about the FreshRSS plugins. on my way to investigate