Post

Siddhant Goel
@sgoel.dev

Looks promising! I also like your LLM policy (that usage is allowed but slop isn't). Concise and makes sense. 👌

chrysn
@chrysn.chaos.social.ap.brid.gy

@peterullrich.com What the FAQ don't cover is comparison to prior art. Does this use an existing forge software such as Forgejo? If so, how does it differ from Codeberg? (Not that it'd *need* to differ, having many forges active is a good thing, but maybe it does.)

Peter Ullrich
@peterullrich.com

It uses a custom git implementation built upon the Rust gitoxide suite and canonical git as oracle with S3 buckets for storage and Postgres for metadata. I just found out that @tangled.org took a similar approach and also wrote a Rust git backend, but disk focused. I’ll write a proper blog soon.

Peter Ullrich
@peterullrich.com

That’s on the roadmap! I’d also love to publish a stream or api lexicon that’d make syncing from and to tangled possible. But that’s a bit further doan the line. First I gotta get the CI ready

Konstantin
@iamkonstantin.eu

Ok nice! I think Forgejo dropped gitea compatibility a while back because of... well, all the gitea issues. I have a tiny fleet of forgejos (even one on a Mac mini) running all the building 🏗️ so it would be cool if I could pushin :)