Gitea — Your Code, Your Server, Your Rules

Gitea is a lightweight, self-hosted Git platform with pull requests, CI/CD via Actions, a package registry, and project boards. It does everything GitHub does for most teams — without sending your source code to someone else's cloud. We run our entire development workflow on Gitea.

How We Use It

Every line of code we write lives in our Gitea instance. Pull requests, code review, Actions runners for CI/CD, container registry for deployments — it's the center of our engineering workflow.

We run multiple Actions runners across different servers for parallel builds. Release automation tags, builds, and deploys without manual steps. The package registry hosts our Go modules and container images.

We also use Gitea's API extensively — our AI agents interact with repositories, create issues, and manage releases programmatically.

What We've Learned Running It

Actions runners need dedicated resources. Sharing CPU with the main Gitea instance leads to slow UI during builds. We deploy runners on separate infrastructure so both stay responsive.

LFS storage grows faster than you expect, especially with binary assets. We set up proper garbage collection schedules and storage quotas from the start so disk usage stays predictable.

What You Get

A fully configured Gitea instance with Actions runners, package registry, and SSH access. Repository mirroring if you want a GitHub backup. SSL, automated backups, monitoring, and updates included. Your code stays on hardware you control.