Raspberry Pi Projects

Gitea: Own Your Code, Track Your Infrastructure You have spent the last nine guides building something real. Docker containers, monitoring, automation workflows, reverse proxies, maybe even a Kubernetes cluster. Your Pi is running production services. Configuration files are scattered across directories. Compose files tuned through trial and error. Environment variables that took three attempts to

n8n: Connect Everything With Visual Workflow Automation You have got a collection of services running on your Pi. Docker containers doing their thing. Uptime Kuma watching them. Ollama summarising text. Pi-hole filtering DNS. Each one works. None of them talk to each other. That is the difference between having containers and having infrastructure. Infrastructure is

Uptime Kuma: Know When Things Break Before Anyone Tells You Here’s a question that changed how I think about my homelab: if Pi-hole goes down at 2am, how would you know? Not how would you fix it — how would you even know it happened? You’d wake up, your family would complain that the internet

Ollama on Raspberry Pi 5: Run Local AI Models on Your Own Hardware Let me set expectations immediately: a Raspberry Pi 5 is not going to replace ChatGPT. It’s not going to run Llama 3 70B. It’s not going to generate images or do real-time voice transcription at any useful speed. What it will do

I’m going to let you in on a secret: the career reason to run Home Assistant has almost nothing to do with home automation. Home Assistant is an event-driven platform with a REST API, a WebSocket API, hundreds of integrations, a state management engine, and YAML-based configuration that follows the exact same patterns as Ansible,

There is a moment in every homelab journey where you realise you have lost track of what is running. You SSH in, type docker ps, and stare at a wall of truncated container names, port mappings, and status fields that tell you technically everything and practically nothing. Which container is eating all the RAM? What