Installer gitea avec Homebrew, apk, chocolatey, Nix, pacman, scoop

Liens du projet

• Page d'accueil
• Dépôt
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• gitea

Historique du projet

Gitea's code lineage includes early Gogs commits from 2014, and the Gitea project identity appears in repository history in 2016 as maintainers replaced Gogs branding and prepared the first 1.0 release. Version 1.0.0 was tagged in December 2016, giving the fork a stable release base under the Gitea name.

After the fork, Gitea broadened from lightweight Git hosting into an all-in-one development platform. The official README describes repository hosting, code management, review, issue tracking, kanban boards, wiki, packages, team collaboration, and CI/CD that can reuse GitHub Actions workflows.

Historique d'adoption

Gitea became important in the self-hosting and package-manager world because it offered a compact alternative to large forge deployments. Its Go implementation, official container image, cross-platform binaries, and presence in major package managers made it easy to deploy on personal servers, small teams' infrastructure, and organizations that prefer owning their source-control service.

The project grew an ecosystem around the core server: official documentation, SDKs, the tea CLI, Gitea Runner, translation infrastructure, cloud offerings, and community-maintained extensions listed through awesome-gitea.

Modes d'utilisation

Practitioners use Gitea as a private or public Git forge. Administrators configure the server through app.ini, run it as a binary, service, or container, and connect it to databases, SSH, reverse proxies, package registries, and Actions runners.

Developers interact with Gitea much like other Git forges: clone and push repositories, open issues and pull requests, manage releases, publish packages, write wiki pages, and define workflows for CI jobs.

Pourquoi les passionnés de paquets s'y intéressent

Gitea is a favorite package-manager entry because one formula or system package can install an entire forge with a small operational footprint. It is often chosen by users who want GitHub-like collaboration without outsourcing the service or running a heavier enterprise stack.

Chronologie

• 2014: Early code lineage begins in the Gogs repository history.
• 2016: Gitea branding and project identity appear in repository history.
• 2016: v1.0.0 is tagged under the Gitea project.
• 2023: Gitea Actions and the runner ecosystem make CI/CD a first-class part of the platform.
• 2026: 1.26.x releases continue the established server release series.

Related projects

• Gitea is related to Gogs through its origin, to Forgejo through later ecosystem divergence, and to tea, go-sdk, and Gitea Runner as official companion projects.

Sources

• https://about.gitea.com/
• https://blog.gitea.com/release-of-1.26.3-and-1.26.4
• https://docs.gitea.com/
• https://github.com/go-gitea/gitea