问HN：为小团队托管Fossil——这是个有趣的选择，还是错误的决定？
我已经在开发一个托管的Fossil SCM服务几个月了，老实说，我不确定这是否是个好主意。今天首页上关于“我们需要一个锻造的联盟”的讨论让我觉得值得发帖分享。
我正在构建的内容：一个Fossil代码库的托管平台。它与代码托管平台有相似的上手体验，但每个项目都是一个独立的SQLite文件，你可以克隆、发送邮件或直接带走。开源的综合解决方案（Django + Postgres + Redis + Caddy + Litestream-to-S3）可以在fossilrepo.io找到。托管版本将很快进入私有测试阶段。
我的粗略论点：
1. Fossil本身就是设计成联邦式的。每个克隆都是整个项目：问题、维基、论坛、历史和代码。这正是当前首页上关于联邦讨论的内容，只不过是使用了一个已有15年以上历史的工具——SQLite项目本身。如果fossil clone可以在任意两个主机之间工作，那么锁定效应基本上就不存在了。
2. AI代理需要集成的上下文。一个Fossil代码库是一个可查询的SQLite文件。代理可以通过SELECT *读取代码、工单、维基和历史，而不是进行47个GraphQL调用。RAG和MCP的设置变得简单易行。此外，还有一个非常易于使用的命令行工具。
3. 小而精的团队服务不足。Git和GitHub在宏观市场上占据了主导地位，这种情况不会改变。但对于1到50人的团队来说，规格、工单、维基和代码都在同一个地方……集成模型显然更好/更简单。
我担心的事情：
- 网络效应——如果没有其他人能找到一个代码库，它就没什么用处。
- 惯性——打破Git的肌肉记忆很难。
- Codeberg / Forgejo / Gitea都是可信的竞争者——如果有的话，什么才是合适的切入点？这是一个有人想要的解决方案吗？
我宁愿现在从HN听到这些，而不是在我们发布后。三个诚实的问题：
- 这有趣吗，还是我在解决一个没人关心的问题？
- 什么会让你真正切换？
- 我遗漏了什么？
此外，我还在为名称而苦恼。两个域名指向同一页面，所以请投票你实际会使用的那个：https://fossilforge.io 或 https://fossilhub.io（我也有.ai版本，但.io感觉更适合开发者）。
查看原文
I've been working on a hosted Fossil SCM service for a few months and I genuinely don't know if it's a good idea. The "We need a federation of forges" thread on the front page today made me think it's worth posting.<p>What I'm building: a hosted home for Fossil repos. Same onramp feel as a code host, but each project is a single self-contained SQLite file you can clone, email, or walk away with. The open source omnibus (Django + Postgres + Redis + Caddy + Litestream-to-S3) is at fossilrepo.io. The hosted version will be in private beta soon.<p>My rough thesis:
1. Fossil is already federated by design. Every clone is the entire project: issues, wiki, forum, history, code. That's the federation discussion happening on the front page right now, just with a 15+ year-old tool the SQLite project itself uses. If fossil clone works between any two hosts, lock-in basically dies.<p>2. AI agents need integrated context. A Fossil repo is one queryable SQLite file. An agent reads code + tickets + wiki + history with SELECT * instead of 47-odd GraphQL calls. RAG and MCP setups become trivial. Also has a cli tool thats super easy to use.<p>3. Small-but-serious teams are underserved. Git+GitHub won the macro market and that's not changing. But the 1-50 person team where the spec, the tickets, the wiki, and the code all belong in the same place... the integrated model is just better/easier.<p>Things I'm worried about:
- Network effect — a repo isn't very useful if nobody else can find it
- Inertia — Git muscle memory is hard to break
- Codeberg / Forgejo / Gitea are all credible
— what's the right wedge, if any? is this a solution that anyone wants?<p>I'd rather hear it from HN now than after we launch. Three honest questions:
- Is this interesting, or am I solving a problem nobody has?
- What would make you actually switch?
- What am I missing?<p>Also stuck on the name. Both domains land on the same page, so vote whichever you'd actually use: https://fossilforge.io or https://fossilhub.io (I also have the .ai versions but .io feels more developer-y)