andrew

andrew / gitgres

Public

Store git objects and refs in PostgreSQL tables. Standard git push/clone work against the database through a libgit2-based backend.

38
2
100% credibility
Found Feb 26, 2026 at 17 stars 2x -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
C
AI Summary

Gitgres enables storing Git repositories entirely within PostgreSQL databases, supporting standard Git operations and SQL queries on repository data.

How It Works

1
🔍 Discover Gitgres

You hear about a handy way to keep all your project's change history safe inside a regular database, so you can search it like any other data.

2
🗄️ Prepare your database space

You set up a fresh spot in your database to store your project's full history of changes and versions.

3
📁 Choose your project

You select the folder holding your project, complete with its timeline of updates and teamwork.

4
🚀 Move history into database

With one easy action, you transfer your entire project history into the database, making it instantly searchable.

5
🔍 Ask questions about changes

You refresh the ready-made lists and start exploring who changed what, when, and why using simple questions.

6
🔄 Work with it normally

You pull the project back to your computer or add new updates, feeling just like using your usual tools.

🎉 History lives in your database

Your project's complete story is now part of your database, super easy to backup, share, and dig into anytime.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 17 to 38 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is gitgres?

Gitgres stores full Git repositories—objects, refs, commits—in PostgreSQL tables using a C backend powered by libgit2. Standard git push/clone work directly against the database via CLI tools (init, push, clone, ls-refs) or a git remote helper (git remote add origin gitgres::dbname=gitgres myrepo). Query history with SQL views on commits/trees, refreshable post-import, plus Docker for instant setup.

Why is it gaining traction?

It ditches filesystem storage for pure database, unlike gitbase (query-only on-disk) or Gitaly (RPC-wrapped FS), enabling one Postgres backup/replica for app + git data. C extension boosts SHA1/tree parsing speed; pure SQL fallback works anywhere with pgcrypto. Hooks devs with Forgejo integration potential—no FS deps.

Who should use this?

Forgejo/Gitea admins consolidating to single-DB stacks; data analysts joining git commits with Postgres tables; containerized git server experimenters avoiding FS volumes. Suits Postgres-heavy teams building custom forges or querying repos via SQL.

Verdict

Solid PoC for DB-backed git (full test suite verifies roundtrips), but 12 stars and 1.0% credibility signal early maturity—scale unproven, though docs/Docker excel. Prototype via Docker; skip prod until more adoption.

(178 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.