What is Rit?
Rit is a Rust library for git's local object/authoring model — loose objects, the index, trees, commits, and ref transactions. It is part of this same codebase as Rithub and Ritgram, but it is honestly scoped: it is a library, not the production forge engine behind rithub.dev today.
What actually runs rithub.dev
Rithub (the git host at rithub.dev) runs on go-gitea/gitea (MIT-licensed, battle-tested, the same engine millions of self-hosted git servers run). Rit is kept in this repository and under active development, but it is not currently the dependency of the deployed forge — see apps/gitea/README.md for the full reasoning behind that decision.
What Rit is, concretely
- A library-first Rust implementation of git's object model: loose blobs/trees/commits/tags, git-exact SHA-1 hashing, canonical object framing.
- An object database (zlib, atomic no-clobber writes, SHA-1 verification on read) and ref storage (HEAD, loose/packed refs, symbolic refs, atomic compare-and-swap updates).
- A checksum-verifying git index (v2/v3) reader/writer, atomic
index.lockmutation, recursive ignore-awareadd, and path-safe status/checkout. - Raw/thin git pack import (via gitoxide) with checksum, delta, and connectivity verification, plus receive-pack/upload-pack protocol handling for push and clone.
- A small
ritCLI (hash-object,cat-file,ls-tree,log,status,add,write-tree,commit,checkout-tree,restore) for exercising the library directly. - Interop-tested against real Git 2.50: objects it writes pass
git fsck, and real Git can read trees/indexes it authors.
What Rit is not
It is not a hosted product, not what serves any page on rithub.dev or ritgram.rithub.dev today, and not something you can sign up for. It is source code in this monorepo, kept rather than deleted, available if a Rust-native forge backend is ever worth finishing independently later.
Looking for the real git host?
That's rithub.dev — see Rithub vs GitHub or import your repos.