diff --git a/README.md b/README.md index d781ea7..69b8992 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,24 @@ # Internal Forge Comparison +This repository lists the pros and cons of three popular open-source Git forges (**GitLab CE**, **Gitea**, and **Forgejo**) based on a side-by-side comparison in a self-hosted test lab on a single VPS ([github.com/matteodelucchi/gitforgelab](https://github.com/matteodelucchi/gitforgelab)). +The goal is to provide a practical reference for teams and organizations evaluating which Git forge best fits their needs, based on real-world usage and feature comparisons. + +## Why This Exists +Choosing the right Git forge for a team or company is not trivial. +Each platform differs in resource usage, feature set, administration complexity, and SSO integration. +This lab deploys all three behind a shared reverse proxy with centralised OIDC authentication so they can be evaluated under identical conditions (same hardware, same identity provider, same workflow). + +The entire infrastructure is defined as code (Terraform + Ansible + Docker Compose) and can be torn down and recreated in minutes. + +## Limitations +This is a **test lab**, not a production deployment. +- Runs on a **single VPS**. There is no high-availability, redundancy, or horizontal scaling. +- **SSH Git access is disabled**; repositories are accessed over HTTPS only. +- All services share **one PostgreSQL and one Redis** instance to save resources. +- GitLab is **memory-tuned aggressively** (2 Puma workers, 5 Sidekiq concurrency) and will be slow under real workloads. +- No backup strategy is included. + +# Comparison ## Quick decision guide | If we want… | Choose | @@ -10,7 +29,6 @@ A more detailed comparison that covers forgejo specific features and limitations is available in the [forgejo.org/compare](https://forgejo.org/compare/). -# Comparison ## Pricing | Feature | GitLab | Gitea | Forgejo | |-------------------------------------------|:------------------:|:-----------------:|:-------------------:|