Gitea is a self-hosted Git service providing a full DevOps platform including repository hosting, issue tracking, pull requests, wiki, CI/CD (Actions), package registry, and more. The architecture is a monolithic Go web application with a Vue.js frontend, using a SQL database (MySQL, PostgreSQL, SQLite, MSSQL) and supporting various storage backends (local, S3, Azure). Key entry points are the web server (port 3000), SSH server (port 22), and CLI commands for administration. Data flows involve Git operations, webhook notifications, and background job queues. External dependencies include Git, a database, and optional services like Redis, Elasticsearch, and object storage. The codebase is well-structured with extensive testing, but carries some technical debt from a long migration history and dual Git backends.
This repository is the full-stack implementation of Mega, a large-monorepo Git hosting and code collaboration platform with a Rust backend and a large React/Next.js frontend. The backend is split into several crates: mono provides the HTTP/SSH API server, ceres contains application services for Git operations, change lists (CLs), code review, build triggers, webhooks and notifications, jupiter handles persistence through SeaORM entities and storage services, jupiter-migrate manages a large sequence of database migrations, and orion/orion-server implement a Buck2-based distributed build orchestration system. The frontend in moon/apps/web is a feature-rich collaboration application with posts, notes, chat, notifications, project management, diff viewing, CL/merge-queue review, admin groups, OAuth integrations, and editor support. The core operational flow is: git push/import -> ceres transport and jupiter storage -> change list and merge-queue workflows -> build triggers sent to Orion -> build events/checks streamed back to the UI.
Gitolite is a Perl-based Git repository management system that provides fine-grained access control, mirroring, and extensibility through a plugin architecture. It operates as a layer on top of plain Git, intercepting SSH and HTTP connections to enforce repository-level and branch-level permissions. Key entry points include `src/gitolite` (CLI) and `src/gitolite-shell` (SSH/HTTP handler). The system compiles a central configuration file into a cached Perl data structure, then uses triggers and VREFs (virtual refs) to enforce rules during push and access operations. Internally, the architecture is modular: core libraries (`Rc.pm`, `Conf/Load.pm`, `Conf/Store.pm`) handle configuration loading and access checks; triggers (e.g., `Mirroring`, `Writable`, `Shell`) extend behavior at lifecycle points; and commands provide admin and user-facing operations. The trigger system and VREF pattern allow third-party extensions without modifying core code. The project includes a substantial test suite with a custom testing DSL (`Tsh.pm`) that simulates SSH and Git operations. External dependencies are minimal: Git, Perl 5.10+, and standard libraries. Optional integrations include Redis for caching, LDAP/FreeIPA for user groups, and HTTP servers for smart-HTTP. The codebase is mature and battle-tested, with over a decade of production use, though some contrib scripts and advanced features (e.g., `EMAIL-CHECK`, `refex-expr`) remain experimental or poorly documented.