Yup, was a Garmin. Part of me has been a little worried cause i can’t find my way anywhere without GPS anymore, and Google has been getting shittier every day.

Hell, I remember the first time I used maps on a computer to plan and print a route, and the first time I could do it online with MapQuest.

Those were moments that the Internet really felt like the future.

You don’t. That’s not what caddy is. Use a bastion for ssh.

Edit: link https://www.redhat.com/sysadmin/ssh-proxy-bastion-proxyjump

The answer to your overarching question is not “common maintenance procedures”, but “change management processes”

When things change, things can break. Immutable OSes and declarative configuration notwithstanding.

OS and Configuration drift only actually matter if you’ve got a documented baseline. That’s what your declaratives can solve. However they don’t help when you’re tinkering in a home server and drifting your declaratives.

I’m pretty certain every service I want to run has a docker image already, so does it matter?

This right here is the attitude that’s going to undermine everything you’re asking. There’s nothing about containers that is inherently “safer” than running native OS packages or even building your own. Containerization is about scalability and repeatability, not availability or reliability. It’s still up to you to monitor changelogs and determine exactly what is going to break when you pull the latest docker image. That’s no different than a native package.

Depends on the specific Zigbee switch, but generally yes.

The magic is in the fact that you can decouple the relay, and use the switch as a sensor that triggers things that may or may not be related to the physical switch position.

The other reason I like it better than a typical “smart switch” is that I can use the shellys with whatever switch I want, so I can have it match my dumb switches and use different colors.

shelly relays will do exactly what you want. just wire them as disconnected switches. i do this to simulate 3-way switches, but it’ll work just as well to swap circuit behavior.

you can use a homeassistant action if you’re already using HA, or you can have the shellys call each others web api when it senses the switch.

Just cause you’ve never seen them doesn’t make it not true.

Try using quadlet and a .container file on current Debian stable. It doesn’t work. Architecture changed, quadlet is now recommended.

Try setting device permissions in the container after updating to Debian testing. Also doesn’t work the same way. Architecture changed.

Redhat hasn’t ruined it yet, but Ansible should provide a pretty good idea of the potential trajectory.

It isn’t. It’s architecture changes pretty significantly with each version, which is annoying when you need it to be stable. It’s also dominated by Redhat, which is a legit concern since they’ll likely start paywalling capabilities eventually.

Every complaint here is PEBKAC.

It’s a legit argument that Docker has a stable architecture while podman is still evolving, but that’s how software do. I haven’t seen anything that isn’t backward compatible, or very strongly deprecated with notice.

Complaining about selinux in 2024? Setenforce 0, audit2allow, and get on with it.

Docker doing that while selinux is enforcing is an actual bad thing that you don’t want.

So… you’re afraid of the command that does the thing you’re trying to do?

I’m surprised no one’s mentioned the security implications. Mounting with nosuid and nodev options can undermine rootkit or privileged escalation exploits.

deleted by creator

deleted by creator

Flatpak is itself a file manager.

That duplicate of your folder in /run is due to filesystem links (or more likely a fuse mount, I’ve never actually looked into how flatpak works). But either way, they aren’t copies of the data.

deleted by creator

Don’t “declutter” manually. Use your package manager.

You’re going to want to look up things like symlinks, hard links, fuse filesystems, and bind mounts among other concepts. Your “whole directory” and other duplicates are artifacts of how the filesystem and process management works, and simply running fsearch or find over them is going to be confusing if you don’t know what you’re looking at.

One Unix concept that carries over to Linux is that everything is a file. Your shared memory space, process data, device driver interfaces, etc, all of it is accessible somewhere in the same virtual filesystem tree as the actual files.

Because of this, there’s very little reason to have the whole filesystem indexed from root. If you’re worried about space usage, you want to work with packages through the package manager. If you’re worried about system integrity, you’ll want package validators.

The above is accurate, and can be considered accurate for any directory below or at well.

Per /run, it’s also mounted in memory, so trying to “declutter” it won’t get you anywhere and things will return on reboot.

Man, I use my switch all the time. But I love little metroidvania and smaller indie and single player games. Any time I see something interesting on steam, I’ll buy it on the switch if available.

I’ve also been using it to replay older stuff. The first red dead, the Arkham trilogy, currently going through Nier: Automata again.

Yup. Treating VMs similar to containers. The alternative, older-school method is cold snapshots of the VM, apply patches/updates (after pre-prod testing & validation), usually in an A/B or red/green phased rollout, and roll back snaps when things go tits up.

deleted by creator