Skip to content

Production usage and project status — context request before adopting #1

@joeblew999

Description

@joeblew999

Hi! Congratulations on ripgit — having looked at the field pretty thoroughly, this is a real strong contender for a self-hosted git server, and honestly the only credible Rust-on-Workers option I could find. The architecture (one DO per repo, SQLite + FTS5, three-way merge inside the DO) is genuinely impressive, and TODOS.md is unusually candid for a side project. Reading the source has been a pleasure.

I'm evaluating ripgit to host my own repos off GitHub (solo developer, ~10 small repos, would self-host the auth worker too). Before I commit, I'd love a quick read on a few things — totally understand if any of these are "no comment":

  1. Production usage — beyond git.theagents.company, is ripgit being run anywhere as a daily-driver remote, by you or others you know of? Trying to gauge how many novel edge cases I'd be the first to hit.

  2. Project status / cadence — last push was March 22, no issues or external PRs filed yet. Is this paused while you focus on gsv and agent-hub, actively being used internally without much public-facing churn, or somewhere in between?

  3. External contributions — are you open to PRs from the outside, and is there a preferred channel (issues here, email, somewhere else)?

  4. Anything you'd want a new adopter to know that isn't in TODOS.md — known footguns, planned breaking changes, things you'd do differently if rewriting today.

Happy to mirror to GitHub in parallel during the trust-building period regardless of the answers — just trying to set realistic expectations on my end.

Thanks again for the project.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions