Automation

Managing one Docker host is easy. Managing four of them is where the small and crazy annoyances start multiplying. One host has a Compose file under /opt. Another has everything under /home/.../docker. A storage box (NAS) has its own container manager. One machine stays on all the time. Another sleeps every night. Updates are easy until you forget which host owns which stack, which Compose file created it, and whether clicking an “update” button actually recreated the Compose project or only replaced a container underneath it. ...

Your Downloads folder is a graveyard. PDFs from 2023, installer files for software you already installed, and random screenshots you took once and never looked at again. And every time you open it, you think: “I should clean this up.” Then you don’t. I built this script because I was tired (and also lazy) of that cycle. It’s not fancy stuff. It just works. The Problem Nobody Talks About Most “cleanup” solutions are too aggressive. They delete stuff you needed. Or they’re too manual, which means you won’t do it. The sweet spot is: ...

Stop treating your Proxmox configuration like it’s disposable. Start treating it like code. GitHub: ruhanirabin/pve-config-git The Problem: Configuration Drift Is a Silent Killer I’ve been running Proxmox for years. Multiple nodes, dozens of VMs, complex network configs, storage pools, custom scripts. And like many of you, I made changes directly on the host. A quick edit to /etc/network/interfaces here, a storage tweak there, a firewall rule adjustment to get something working. ...