explaingit

go-gitea/gitea

🔥 Hot★ 55,755GoAudience · ops devopsComplexity · 4/5ActiveLicenseSetup · hard

TLDR

Self-hosted Git service that runs on your own servers, giving you a GitHub-like experience with full control over your source code and infrastructure.

Mindmap

mindmap
  root((Gitea))
    What it does
      Git repository hosting
      Code review and PRs
      Issue tracking
      CI/CD workflows
    Features
      Package registry
      Container registry
      Web interface
      Team collaboration
    Tech stack
      Go backend
      Node.js frontend
      PostgreSQL MySQL SQLite
    Use cases
      Privacy compliance
      Avoid vendor lock-in
      Low-power hardware
    Deployment
      Single binary
      Linux macOS Windows
      Raspberry Pi support

Things people build with this

USE CASE 1

Run a private Git server on your own hardware for a team without paying for cloud hosting.

USE CASE 2

Store source code on infrastructure you control to meet privacy or compliance requirements.

USE CASE 3

Host a package registry and container registry alongside your repositories for a complete development platform.

USE CASE 4

Set up automated CI/CD pipelines using GitHub Actions-compatible workflows on your own servers.

Tech stack

GoNode.jspnpmPostgreSQLMySQLSQLiteDocker

Getting it running

Difficulty · hard Time to first run · 1day+

Requires database setup (PostgreSQL/MySQL/SQLite), Go/Node.js build, and Docker orchestration; multiple moving parts to configure.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice and license text.

In plain English

Gitea is a self-hosted Git service, meaning it lets you run your own version of a platform similar to GitHub or GitLab entirely on your own servers. The core problem it solves is giving teams and individuals full ownership over their source code infrastructure without relying on a third-party cloud provider. You install Gitea on a server you control, and it provides a web interface for managing Git repositories, reviewing code, collaborating with a team, and running automated workflows. Gitea includes a broad feature set: Git repository hosting with a web interface, pull request and code review workflows, issue tracking, a built-in package registry for publishing software packages, a continuous integration and deployment system (CI/CD) compatible with GitHub Actions workflows, and a Docker-compatible registry for storing container images. Because it is written in Go, it compiles to a single binary that runs efficiently even on low-powered hardware like a Raspberry Pi, and it supports Linux, macOS, Windows, and various CPU architectures. You would use Gitea if you want a GitHub-like experience on infrastructure you own and control, if you have privacy or compliance requirements that prevent using cloud-hosted services, or if you want to avoid vendor lock-in. It is a popular choice for small teams, self-hosting enthusiasts, and organizations that need an affordable alternative to hosted services. The tech stack is Go for the backend with a frontend built using Node.js and the pnpm package manager, and it uses a PostgreSQL, MySQL, or SQLite database for storage.

Copy-paste prompts

Prompt 1
How do I install Gitea on a Linux server and set up my first Git repository with a web interface?
Prompt 2
Show me how to configure Gitea CI/CD to run GitHub Actions workflows on my self-hosted instance.
Prompt 3
What's the best way to back up and restore a Gitea instance running on PostgreSQL?
Prompt 4
How do I set up Gitea's package registry to publish and pull Docker images and software packages?
Prompt 5
Can I migrate my repositories from GitHub to a self-hosted Gitea server, and how?
Open on GitHub → Explain another repo

Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.