https://backend-engineering-strategy-tools.github.io/site/tags/forgejo/Recent content in Forgejo on Backend Engineering Strategy ToolsHugo -- gohugo.ioen-usMon, 01 Jan 2024 00:00:00 +0000https://backend-engineering-strategy-tools.github.io/site/public-notes/cicd/gitea/Mon, 01 Jan 2024 00:00:00 +0000https://backend-engineering-strategy-tools.github.io/site/public-notes/cicd/gitea/<p><strong><a class="link" href="https://gogs.io/" target="_blank" rel="noopener" >Gogs</a></strong> came first — a self-hosted Git service, lightweight, single binary, runs anywhere. Think GitHub but on your own infrastructure. Simple to deploy, easy to understand, and that was the point.</p> <p>Gitea forked from Gogs in 2016 and has moved considerably faster since — more features, more active development, more community. For any new self-hosted Git deployment, Gitea became the natural choice over Gogs. Unless you look at where Gitea itself is heading.</p> <h2 id="forgejo">Forgejo </h2><p>Gitea has been drifting toward the enterprise and commercial end. The governance has shifted, cloud services have been prioritised, and the community-first ethos that made it attractive has weakened.</p> <p><strong><a class="link" href="https://forgejo.org/" target="_blank" rel="noopener" >Forgejo</a></strong> is the community response — a fork of Gitea maintained by the Codeberg team, focused on staying open, community-governed, and free. It is a drop-in replacement: same API, same data format, same deployment model. Migrating from Gitea to Forgejo is straightforward.</p> <p>For new deployments today, Forgejo is the better choice. Gitea is still solid and maintained, but the trajectory matters.</p> <p><a class="link" href="https://codeberg.org/" target="_blank" rel="noopener" >Codeberg</a> — the public hosting platform run by the Forgejo maintainers — is worth knowing about as a GitHub alternative for open source projects.</p> <h2 id="features">Features </h2><ul> <li>SSH and HTTPS repository access</li> <li>Issues, pull requests, code review, wiki, protected branches</li> <li>Webhooks and Git hooks</li> <li>Deploy keys and fine-grained access tokens</li> <li>LDAP, SMTP, OAuth, OIDC authentication</li> <li>PostgreSQL, MySQL, SQLite support</li> <li>Built-in container registry</li> <li>Gitea Actions / Forgejo Actions — GitHub Actions-compatible CI</li> </ul> <h2 id="issues">Issues </h2><p>The issue tracker covers the basics well:</p> <ul> <li>Numeric ID, description, comment thread</li> <li>Assignable to users, file attachments, labels, milestones</li> <li>Open/closed state per repository</li> </ul> <p><img alt="Issue view" class="gallery-image" data-flex-basis="300px" data-flex-grow="125" height="640" loading="lazy" sizes="(max-width: 767px) calc(100vw - 30px), (max-width: 1023px) 700px, (max-width: 1279px) 950px, 1232px" src="https://backend-engineering-strategy-tools.github.io/site/public-notes/cicd/gitea/issue.png" width="800"></p> <p>Default labels — fully customizable:</p> <p><img alt="Labels" class="gallery-image" data-flex-basis="300px" data-flex-grow="125" height="640" loading="lazy" sizes="(max-width: 767px) calc(100vw - 30px), (max-width: 1023px) 700px, (max-width: 1279px) 950px, 1232px" src="https://backend-engineering-strategy-tools.github.io/site/public-notes/cicd/gitea/labels.png" width="800"></p> <p>Organisation-wide issue overview:</p> <p><img alt="All issues" class="gallery-image" data-flex-basis="300px" data-flex-grow="125" height="1760" loading="lazy" sizes="(max-width: 767px) calc(100vw - 30px), (max-width: 1023px) 700px, (max-width: 1279px) 950px, 1232px" src="https://backend-engineering-strategy-tools.github.io/site/public-notes/cicd/gitea/all_issues.png" srcset="https://backend-engineering-strategy-tools.github.io/site/public-notes/cicd/gitea/all_issues_hu_c8e014b11f98ca1d.png 800w, https://backend-engineering-strategy-tools.github.io/site/public-notes/cicd/gitea/all_issues_hu_47f7964cb5b07fff.png 1600w, https://backend-engineering-strategy-tools.github.io/site/public-notes/cicd/gitea/all_issues.png 2200w" width="2200"></p> <h2 id="resources">Resources </h2><ul> <li><a class="link" href="https://forgejo.org/" target="_blank" rel="noopener" >Forgejo</a> — community fork, recommended for new deployments</li> <li><a class="link" href="https://gitea.io/" target="_blank" rel="noopener" >Gitea</a></li> <li><a class="link" href="https://gogs.io/" target="_blank" rel="noopener" >Gogs</a> — where it all started</li> <li><a class="link" href="https://codeberg.org/" target="_blank" rel="noopener" >Codeberg</a> — public Forgejo hosting</li> </ul>