No actual technical solution here, but it smells slightly of XY-Problems.
From what you described it seems the main issues are
Maybe you could look into solutions like setting a custom ringtone for important callers or having the phone announce caller names so your mother can decide if she wants to make the effort to get her phone.
I’m speculating a bit here but I can imagine that getting up and answering the phone is exhausting for your mother. Also if her mindset is " a ringing phone means it’s important" that could make it even more stressful.
Maybe you could find a way to let her silence all calls except caregivers and ICE contacts. (On Android DND exceptions could work for that)
That way she doesn’t feel pressured to answer the phone every time it rings and stays reachable.
If it’s actually just the physical issue of reaching the phone in time, does she have a convenient way to carry the phone indoors like a lanyard?
Hope some of this helps you
That’s the equivalent of leaving the door open and hanging a sign “Internet over there” pointing at a wall.
Programs don’t need to respect those registry keys. If you’re worried about internet access, set up a firewall.
Also, if you’re worried about malware, the damage is probably done before anything connects to the internet.
I run a 2 node k3s cluster. There are a few small advantages over docker swarm, built-in network policies to lock down my VPN/Torrent pod being the main one.
Other than that writing kubernetes yaml files is a lot more verbose than docker-compose. Helm does make it bearable, though.
Due to real-life my migration to the cluster is real slow, but the goal is to move all my services over.
It’s not “better” than compose but I like it and it’s nice to have worked with it.
You dynamically request “a port” from the vpn gateway and it returns your port number.
As long as your nat-pmp-client keeps refreshing the port, it should stay the same. The timeout is rather low (60s afaik) so it probably wouldn’t survive restarts.
There’s a docker image that automates this for qbittorrent, but it shouldn’t be overly complicated to adapt the script to other clients, if they can be configured via an API.
Thanks for the pointers that sounds quite doable. I’ll give it a shot to mash it into my helm chart. Will report back.
Edit:
Got ProtonVPN and qbittorrent working with manual port-forwarding. The natmap-docker image wants to use the docker socket which is not available in my kubernetes cluster.
I’m currently reworking the script to run without docker access.
Yeah, inductive charging is basically a must.
Especially because it eliminates the guesswork if the watch is correctly seated to charge