[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2fessz2vhkwcj":3},{"code":4,"message":5,"data":6,"timestamp":74},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":45,"summary_md":46,"topic":47,"github_topics":50,"license":70,"homepage":71,"updated_at":72,"history":73},"go-gitea\u002Fgitea",7,"Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI\u002FCD","Go",58678,7310,169,3645,[16,22,28,34,40],{"id":17,"title":18,"points":19,"comments":20,"posted_at":21},17260221,"Giteabot account was compromised",134,60,"2018-06-07",{"id":23,"title":24,"points":25,"comments":26,"posted_at":27},41488929,"Gitea blocks PR from community, charging $$ for open-source contributions",68,79,"2024-09-09",{"id":29,"title":30,"points":31,"comments":32,"posted_at":33},18981570,"Gitea v1.7.0",25,2,"2019-01-23",{"id":35,"title":36,"points":37,"comments":38,"posted_at":39},27832020,"5000€ bounty to implement forgefed federation for Gitea",6,1,"2021-07-14",{"id":41,"title":42,"points":43,"comments":38,"posted_at":44},22471503,"Self-Hosted Git Service",4,"2020-03-03","A self-hosted, single-binary alternative to GitHub\u002FGitLab for teams that need Git hosting, review, CI and package registry on their own hardware.","## The problem\n\nOnce a team outgrows a few Git remotes, it usually wants review, issues, wikis, a package registry and CI in one place. SaaS options mean paying per seat and handing source code to a third party; self-managed GitLab means running a large Ruby\u002FPostgres stack. Gitea answers this by giving you the whole collaboration surface as one Go binary you can run on almost anything, from a Raspberry Pi to a company VM.\n\n## What's different\n\nThe usual approaches are a SaaS host, GitLab, or stitching together separate tools (Gogs, a registry, a CI server). Gitea's bet is breadth in a small footprint: Git hosting, issues, kanban, wiki and package registry in a single process, plus an Actions-compatible CI that can reuse existing GitHub Actions workflows. Written in Go, it cross-compiles across Linux, macOS, BSD and Windows on x86, ARM, RISC-V and PowerPC, so an old ARM box is a valid deployment target. The trade-off is depth: it is not trying to match GitLab's enterprise module ecosystem, and the README itself is mostly links to external docs rather than a feature tour.\n\n## Who it's for\n\nSmall to mid-size engineering teams, homelabs, universities and anyone under a data-residency or air-gap requirement who wants a boring, low-maintenance forge. It suits people who already know Git and just want the surrounding plumbing without a managed service. Look elsewhere if you need deep enterprise integrations, heavy compliance auditing, or if you are unwilling to own server patching, backups and upgrades — a hosted forge is genuinely less work.\n\n## Cost of adoption\n\nYou supply a server, ideally a database (SQLite is offered but not the right pick for multi-user production), and ongoing upgrade discipline. Container images and a demo instance exist, and the project ships its own documentation site, CLI (`tea`), SDK and Actions runner. MIT license is permissive, so embedding or rebranding is allowed. Security is the real cost: a self-hosted forge is a high-value target, and the project's most prominent Hacker News thread is a 2018 report of a compromised bot account — an old incident, but a reminder that instance hardening and prompt patching are on you. Expect occasional breaking changes across releases and a migration path you should test before upgrading.\n\n## Verdict\n\nThis is not a new project riding a spike: it has been on GitHub since November 2016, has roughly 58.7k stars and 7.3k forks, and a weekly Go trending appearance (+169 stars, #7 in late October 2026) reads as steady, mature interest rather than a launch. Its longevity and the MIT license make it a safe long-term dependency for a team that wants a lightweight self-hosted forge. It is the pragmatic middle ground between a SaaS subscription and a full GitLab deployment, but it does not erase the operational burden — you trade vendor management for server management. Adopt it if you want to own the box and keep the stack small; skip it if you want zero-maintenance collaboration.",{"slug":48,"name":49},"devops","DevOps & Self-hosting",[51,52,48,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69],"bitbucket","cicd","docker-registry-v2","git","git-gui","git-lfs","git-server","gitea","github","github-actions","gitlab","go","golang","hacktoberfest","maven-server","npm-registry","self-hosted","typescript","vue","MIT","https:\u002F\u002Fgitea.com","2026-10-25T00:36:42Z",[],1792904975]