gogs: A simple, stable and extensible self-hosted Git service that can be set up in the most painless way.
What problem it solves
Teams and individuals need a straightforward way to host and manage their own Git service. Self-hosting requires code hosting, collaboration tools, authentication, integrations, database configuration, and deployment options in one extensible system.
Key features
Code hosting and repository browsing — Host repositories over SSH and HTTP(S), with deploy keys and LFS, and browse, edit, search and blame code in the browser. Repositories can also be migrated or mirrored from other code hosts.
Source: README
Collaboration and organization management — Use issues, wikis, pull requests, inline reviews, protected branches, organizations, teams, and collaborators to support work around shared repositories. The README marks inline reviews, stacks, code owners, and signed commits as in development.
Source: README
Flexible authentication and security controls — Sign in through LDAP, SMTP, PAM, reverse proxy, OAuth 2.0, OpenID Connect, or SAML 2.0, with additional options for two-factor authentication and passkeys. Session management, security alerts, and breached password detection are also listed, with several marked as in development.
Source: README
Deployment and database options — Deploy the service as a single binary, with Docker, or with Kubernetes, across Linux, macOS, Windows, and ARM. Choose PostgreSQL, MySQL, or SQLite3 for storage.
Source: README, Dockerfile
APIs, webhooks, and observability — Connect external workflows through webhooks for Slack, Discord, DingTalk, and other services, plus server-side Git hooks. The service also offers an experimental REST API and OpenTelemetry with a built-in trace viewer.
Source: README
Who it may suit
Inference: may suit teams and individual developers who want to operate a self-hosted Git service with repository collaboration, configurable authentication, and flexible deployment options.
Topics to discuss
Which deployment format should receive the clearest setup documentation for different operating systems?
How should the community prioritize planned collaboration, security, and observability features?
Which integrations and API workflows should be documented with complete community examples?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/gogs/gogs#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…