Forgejo

Self-Hosting Woodpecker CI: Lightweight Continuous Integration Most self-hosted CI/CD tools are either overkill for a homelab or painful to configure. Jenkins needs a PhD in XML. GitLab CI requires GitLab. GitHub Actions is locked to GitHub’s cloud (or a heavyweight self-hosted runner setup). Woodpecker CI takes a different approach: a lightweight, container-native CI/CD engine that uses ~100 MB of RAM for the server and ~30 MB per agent. It’s a community fork of Drone CI (before the license change), fully open source under Apache 2.0, and used in production by Codeberg — one of the largest community Git hosting platforms. ...

Want to host your own code without relying on GitHub or GitLab? Forgejo is a community-driven fork of Gitea — lightweight, fast, and designed to stay free forever. It’s everything you need for private repos, CI/CD, and team collaboration on your own hardware. Why Forgejo Over Gitea? Forgejo forked from Gitea in 2022 after governance concerns. The key differences: Community-governed — no single company controls it Guaranteed free — committed to staying FOSS, no enterprise bait-and-switch Federation support — working toward ActivityPub integration (follow repos across instances) Same codebase — if you know Gitea, you know Forgejo Drop-in replacement — migrate from Gitea with zero data loss Prerequisites Docker and Docker Compose ~256MB RAM (runs great on a Pi) A domain (optional but recommended) Step 1: Setup mkdir -p ~/forgejo && cd ~/forgejo Step 2: Docker Compose Create docker-compose.yml: ...