For users
Everyday workflows on a git-shark instance: organisations, collaborators, forks, releases, 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, CI runner registration, and bot protection.
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
- Releases published from tags, with generated zip and tar.gz source archives
- Forgejo/Gitea-compatible CI: workflows run on push, with logs and commit statuses
- Push mirrors to external remotes with encrypted credentials
- Opt-in ForgeFed / ActivityPub federation between instances
- Metered expensive pages with an optional Turnstile/hCaptcha bot check
- JSON REST API and an MCP server sharing one token model