Git

Self-Hosting Gitness (Harness Open Source): Modern Git Hosting with Built-In CI/CD Most self-hosted Git solutions make you bolt on CI/CD as an afterthought. You set up Gitea, then add Woodpecker or Drone, configure webhooks, manage two sets of credentials, and pray the integration doesn’t break during updates. Gitness — now officially Harness Open Source — takes a different approach. It’s a single binary that ships Git hosting, CI/CD pipelines, code review, secret scanning, and cloud developer environments in one package. Born as the next generation of Drone CI, it inherits Drone’s container-native pipeline philosophy while adding a complete source control layer on top. ...

If you’ve ever wanted your own private GitHub without the complexity of GitLab or the resource hunger of enterprise solutions, Gitea is your answer. It’s a lightweight, self-hosted Git service written in Go that runs happily on a Raspberry Pi while still offering pull requests, issues, CI/CD, and package registries. Gitea uses minimal resources (typically under 200MB of RAM) and starts in seconds. It’s the perfect fit for home labs, small teams, and anyone who wants full control over their code. ...

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: ...