[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fpffy4sumz7ks":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","适合想把 Git 托管、代码评审、CI 和包仓库都放在自己服务器上的团队，单二进制替代 GitHub\u002FGitLab。","## 解决什么问题\n\n团队一旦过了「几个 Git 远程仓库」的阶段，通常就会需要代码评审、Issue、Wiki、包仓库和 CI 集中在一处。用 SaaS 要按人头付费，还得把源码交给第三方；自建 GitLab 则意味着维护一整套体积不小的 Ruby\u002FPostgres 服务。Gitea 的做法是把这些协作能力打包成一个 Go 单二进制，从树莓派到公司虚拟机都能跑。\n\n## 有什么不同\n\n常见方案无非三种：托管 SaaS、GitLab，或者把 Gogs、独立制品库、独立 CI 拼在一起。Gitea 的取舍是「小而全」：Git 托管、Issue、看板、Wiki 和包仓库跑在同一个进程里，CI 兼容 GitHub Actions，可以直接复用现有 workflow。Go 写的另一个好处是交叉编译覆盖 Linux、macOS、BSD、Windows 以及 x86、ARM、RISC-V、PowerPC，老 ARM 设备也是合理的部署目标。代价是深度：它不打算对齐 GitLab 那套企业模块生态，README 本身也主要是外链文档，而非功能导览。\n\n## 适合谁\n\n适合中小研发团队、homelab 玩家、高校，以及有数据驻留或内网隔离要求、只想要一个「省心代码托管」的组织。你熟悉 Git，只想把周边配套自己管起来，它就是对的。反过来，如果需要深度企业集成、复杂合规审计，或者不愿意承担打补丁、备份、升级这些运维责任，那托管服务确实更省事。\n\n## 上手成本\n\n需要一台服务器，生产环境建议配独立数据库（SQLite 可用但多人场景不是好选择），还要有持续的升级纪律。官方提供容器镜像和演示站，项目自带文档站、CLI（`tea`）、SDK 和 Actions runner，MIT 协议很宽松，嵌入或换品牌都可以。真正的成本在安全：自建代码托管是高价值目标，该项目在 Hacker News 上最热的一条讨论是 2018 年机器人账号被入侵的事件——事情很旧，但提醒你实例加固和及时打补丁得自己负责。跨大版本升级偶有破坏性变更，上线前最好先演练迁移。\n\n## 点评\n\n这不是蹭热度的新项目：2016 年 11 月就已在 GitHub 上，约 58.7k star、7.3k fork；2026 年 10 月底还上了 Go 周榜第 7（一周 +169 star），说明关注度是稳定而非爆发式的。长期存在加上 MIT 协议，让它对想要轻量自托管 forge 的团队来说是可靠的长期依赖。它处在 SaaS 订阅和完整 GitLab 部署之间的务实位置，但没有消除运维负担——你只是把供应商管理换成了服务器管理。愿意自己管机器、想保持技术栈精简就用它；想要零维护协作，就别选。",{"slug":48,"name":49},"devops","运维与部署",[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",[],1792901898]