For a FAQ on how Forgejo and Gitea are related, see the dedicated comparison page.
Forgejo (pronounced /forˈd͡ʒe.jo/) is inspired by forĝejo, the Esperanto word for forge.
The Forgejo domains are in the custody of Codeberg e.V. a non-profit based in Germany and dedicated to hosting Free Software projects since 2019. It is ultimately in control of Forgejo and its bylaws guarantee it will keep further the interest of the general public. No trademark was registered at this point in time.
Codeberg e.V. is an association registered in Berlin, Germany. The e.V. abbreviation is for eingetragener Verein, which translates as ‘registered association’. The link above is to the Impressum, which includes the required contact information, statements regarding non-profit status, and other helpful information. You may verify this information via the German Federal Registration portal; just type in
Codeberg e.V. as the company, click the Find button, and select the SI link for an xml structured report.
Sustaining Free Software projects developed in the interest of the general public is an ongoing challenge. Forgejo relies on a mixture of volunteer contributions, grants, donations and employee delegation to keep going. The details are documented transparently in a repository dedicated to sustainability.
The largest known public instances are:
See also the list of instances maintained in the page dedicated to Forgejo related resources.
Forgejo is a collective of individuals who define their own governance. Its evolution is discussed in a dedicated forum until an decision is made and documented. Codeberg e.V. does not run the day to day operations of Forgejo nor does it require the members of the project to follow its governance. It is solely responsible for ensuring the domains and trademarks are ultimately used to further the interest of the general public in accordance to its bylaws.
No. The license of Forgejo is MIT. It was suggested to change the license to AGPL in order to prevent a takeover from a for-profit company. It was however decided that the best way to prevent such a takeover was to have the Forgejo domains and trademarks in the custody of the Codeberg e.V. non-profit.
Security issues are managed by a team sharing the effort between Codeberg and Forgejo.
The security team is available at
email@example.com (GPG public key 1B638BDF10969D627926B8D9F585D0F99E1FB56F) and is tasked to identify, define, and respond to vulnerabilities.
The 1.19 tag is set to be the latest patch release, starting with 1.19.0-2. 1.19 will then be equal to 1.19.1-0 when it is released and so on. It can conveniently be used for automated upgrades to the latest stable release.
Because upgrading from 1.X to 1.X+1 (for instance from 1.18 to 1.19) requires a manual operation and human verification. However it is possible to use the X.Y tag (for instance 1.19) to get the latest point release automatically.
Forgejo introduces two new themes: light version named forgejo-light and a dark version named forgejo-dark. They are the default for a new installation but will need to be set explicitly if the
app.ini file already has a custom list of themes. For instance, if it looks like this:
[ui] THEMES = gitea-auto,gitea-light,gitea-dark
the forgejo-auto, forgejo-light and forgejo-dark can be added as follows:
[ui] THEMES = forgejo-auto,forgejo-light,forgejo-dark,gitea-auto,gitea-light,gitea-dark
Although the Forgejo codebase is known to be easy to built for Windows and reliably run with a mssql database, there currently is no expertise on either of those in the Forgejo community. Maintaining a distribution targetting a given database and Operating System requires someone to build and maintain the release pipeline, figure out the root cause of bugs and fix them.