PUBLISHED ARTIFACT // gitea
Lightweight self-hosted software development and Git collaboration
services:
server:
image: docker.gitea.com/gitea:1.26.3
restart: unless-stopped
environment:
USER_UID: "1000"
USER_GID: "1000"
ports:
- "3000:3000"
- "222:22"
volumes:
- ./gitea:/dataOfficial guidance says 2 CPU cores and 1 GB RAM are typically sufficient for small teams; storage grows with repositories, packages, attachments, and Actions artifacts.
The container includes Git and can use built-in SQLite or an external PostgreSQL, MySQL, MariaDB, or MSSQL database. Persistent /data storage is required.
Built-in accounts plus LDAP, OAuth2/OIDC, and trusted reverse-proxy header authentication are supported.
For a consistent backup, stop Gitea and preserve the database, repositories, configuration, attachments, packages, and other /data content together. Gitea also provides a dump command; restores are manual and should be rehearsed.
Actions execution requires separate runners. Large or highly available installations need external database, storage, and operational planning beyond the basic single-host Compose example.
Gitea emphasizes a familiar all-in-one Git service and broad integrations; operators prioritizing independent community governance should compare it directly with Forgejo.