
Lazy SRE Automation: How n8n and Ollama Write Their Own Pull Requests When Servers Crash
·1008 words·5 mins
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.
