For users
Everyday workflows on a git-shark instance: organisations, collaborators, forks, push mirrors, federation, profile settings, and connecting AI clients over MCP.
For admins
Deploy and operate an instance: Docker Compose setup, TLS and OIDC, persistent data, the configuration reference, federation operations, and CI runner registration.
For maintainers
Architecture notes and design decisions: ForgeFed internals, push-mirror queue design, fork mechanics, the runner protocol, and the federation roadmap.
What git-shark does
- Bare Git repositories served over smart HTTP and SSH
- Single natively-compiled Quarkus service — one container, fast startup
- Server-rendered Qute web UI, fully functional without JavaScript
- OIDC login with PostgreSQL metadata and per-repository access control
- Organisations, collaborators, forks, issues, and merge requests with line comments
- Push mirrors to external remotes with encrypted credentials
- Opt-in ForgeFed / ActivityPub federation between instances
- JSON REST API and an MCP server sharing one token model