@@ -1,8 +1,8 @@ |
| 1 |
# dumbforge |
1 |
# dumbforge |
| 2 |
|
2 |
|
| 3 |
Well, everyone's [been talking about GitHub alternatives](https://mitchellh.com/writing/ghostty-leaving-github) lately. I'm pretty sympathetic to that on an ideological level (and just the fundamental problem of it being down all the time), but historically the alternatives kind of suck, and I think still miss the point of Git being decentralized in the first place. Gitea/Forgejo are cool, but require you to set up a server and configure it. Even though it's pretty easy, it's still annoying and requires you to pay for and babysit a VPS or whatever to run the forge program. Codeberg has been a platform of choice for freedom-heads to get away from GitHub, but they recently instituted a no-crypto and no-LLM rule. I respect what they're doing, but I'm pretty AI-pilled so that's not going to work for me. |
3 |
Well, everyone's [been talking about GitHub alternatives](https://mitchellh.com/writing/ghostty-leaving-github) lately. I'm pretty sympathetic to that on an ideological level (and just the fundamental problem of it being down all the time), but historically the alternatives kind of suck, and I think still miss the point of Git being decentralized in the first place. [Gitea](https://gitea.com/)/[Forgejo](https://forgejo.org/) are cool, but require you to set up a server and configure it. Even though it's pretty easy, it's still annoying and requires you to pay for and babysit a VPS or whatever to run the forge program. [Codeberg](https://codeberg.org/) has been a platform of choice for freedom-heads to get away from GitHub, but they recently instituted a no-crypto and no-LLM rule. I respect what they're doing, but I'm pretty AI-pilled so that's not going to work for me. |
| 4 |
|
4 |
|
| 5 |
It occurred to me that you don't actually need to run a forge or git daemon at all, since Git supports cloning via the so-called ["dumb" HTTP protocol](https://git-scm.com/book/en/v2/Git-Internals-Transfer-Protocols). You could theoretically just throw your git repo into an s3 bucket, and it would be clone-able, no daemon or VPS required. So that's cool, and even more decentralized; but the problem with self-hosting git like that, is that then you don't have the nice landing page, file browser, commit log, etc etc. It's small, but it makes a big difference to have a GitHubby UI for each project. SourceHut and Savannah struggle with this I think, since they're pretty alien to normies. |
5 |
It occurred to me that you don't actually need to run a forge or git daemon at all, since Git supports cloning via the so-called ["dumb" HTTP protocol](https://git-scm.com/book/en/v2/Git-Internals-Transfer-Protocols). You could theoretically just throw your git repo into an s3 bucket, and it would be clone-able, no daemon or VPS required. So that's cool, and even more decentralized; but the problem with self-hosting git like that, is that then you don't have the nice landing page, file browser, commit log, etc etc. It's small, but it makes a big difference to have a GitHubby UI for each project. [SourceHut](https://sourcehut.org/) and [Savannah](https://savannah.gnu.org/) struggle with this I think, since they're pretty alien to normies. |
| 6 |
|
6 |
|
| 7 |
So I slopped `dumbforge` together as a proof of concept; it's a static-site-generator like thing that functions as a git adapter which pushes directly to an s3 bucket, and generates a GitHub-like UI. So you get some really nice advantages: |
7 |
So I slopped `dumbforge` together as a proof of concept; it's a static-site-generator like thing that functions as a git adapter which pushes directly to an s3 bucket, and generates a GitHub-like UI. So you get some really nice advantages: |
| 8 |
|
8 |
|
Nick Faro committed on