Skip to main content

Automation

From Prometheus Alerts to 500 Job Apps: When My SRE Agent Terrorized LinkedIn

It is a well-established law of homelab physics: if a task can be automated, it will be automated—until it violently consumes your entire digital existence. In our Night-Tower setup, our self-hosted Hermes Agent (containerized on docker-vm and wired to NVIDIA’s Nemotron 70B endpoint) has had exactly one job for the past six months: ruthless Site Reliability Engineering. Hermes lives in a world of pure, unadulterated paranoia. Her brain only understands five nines of uptime (99.999%), CPU thermal throttling, killing runaway memory leaks with SIGKILL -9, and screaming into our private Discord channel whenever a ping packet dares to take longer than 2.4 milliseconds. So, naturally, when I got tired of scrolling through the endless dystopian wasteland of modern DevOps job listings demanding 70 job titles, I had a brilliant 2:00 AM homelab idea: “Hermes, write a browser automation script, parse LinkedIn jobs, tailor my resume to pass ATS filters, and submit applications for senior infrastructure roles. Keep it efficient.” Twelve minutes later, my LinkedIn account was flagged for automated domestic terrorism, a Fortune 500 VP of Talent received a P0 PagerDuty escalation alert, and I was officially in the candidate pool for Chief Astronaut at NASA.

Lazy SRE Automation: How n8n and Ollama Write Their Own Pull Requests When Servers Crash

Getting woken up by an alert at 2:15 AM because a container crashed on a port conflict is a rite of passage every DevOps engineer despises. Standard engineering response: Wake up, open your laptop in the dark, SSH into the host, parse docker logs, realize a memory limit or port mapping is misconfigured, edit the docker-compose.yml, commit the fix, and go back to sleep angry. Lazy homelab engineering response: Build an automated n8n + Vector + Ollama AI pipeline that catches the crash log, diagnoses the root cause, writes the code patch, creates a Git branch, opens a Pull Request, and pings your phone on Discord so you can click “Merge” without leaving bed. Here is how I built the SRE Log Triage & Auto-PR Workflow using n8n—the premier open-source workflow automation platform.

Death to TL;DR: Fighting Unnecessary Tech Abbreviations with n8n, Ollama & Discord

Reading modern technical documentation has officially turned into deciphering WWII Enigma machine code. You open a blog post expecting a simple explanation of a system, and within three paragraphs you are hit with: “Our CI/CD pipeline deploys an eBPF probe into a K8s pod using ACME TLS certs stored in 1P, monitored via PROM and logged to LOKI (TL;DR: it works).” Whatever happened to using actual words? When did software engineering decide that typing six extra letters was a medical emergency? I genuinely detest unnecessary tech abbreviations. And because I am a homelab engineer, I didn’t just complain about it—I built an automated n8n + Ollama AI Acronym Police bot (building on my n8n multi-LLM orchestration setup) to catch abbreviations red-handed and force them to explain themselves on Discord.