How josh-project/josh works
Project type and purpose
• This is a polyglot monorepo for a full-stack “Git history filtering proxy” system (“josh-project”).
It comprises:
• A Rust-based proxy service (josh-proxy) exposing HTTP, SSH and GraphQL endpoints.
• A React front-end (josh-ui) for browsing/filtering repo contents.
• Core filtering and history-manipulation libraries in Rust (josh-core, josh-filter, josh-rpc, josh-graphql).
• Auxiliary components (CGI, reverse-proxy, SSH shell, LFS test server).
• Docker/S6 init scripts to package the service.
File structure
• Top level:
• Docker configuration (Dockerfile, docker/, S6 scripts).
• Cargo workspace crates:
– hyper-reverse-proxy, hyper_cgi (HTTP/CGI plumbing)
– josh-core (filter engine, history, workspace logic)
– josh-filter (CLI shim)
– josh-rpc (async IO, RPC helpers)
– josh-graphql (GraphQL schema and resolvers)
– josh-proxy (main HTTP/SSH/GraphQL server)
– josh-ssh-shell & josh-ssh-dev-server (SSH integration)
– josh-ui (React SPA)
• Go-based LFS test server.
• Extensive integration tests under tests/.
README for additional insights
• Core use cases: partial cloning, workspace composition, CI/CD sandboxing, GraphQL API, caching proxy.
• The proxy sits in front of any Git host, mounts a local volume for cached repos, and exposes:
• HTTP Git transport
• SSH Git transport
• GraphQL API
• Static UI assets