Get Forgejo

You can get the binaries or container images for Forgejo as explained below. For more information on how to setup and configure Forgejo, checkout the installation guide.

Installation from binary

Download

The following instructions are for installing the latest Forgejo release on a Linux system with the amd64 architecture.
For other platforms and architectures, be sure to find the appropriate files and modify the instructions below accordingly.
A mirror of the releases is available in case codeberg.org can not be accessed. To use it replace codeberg.org with code.forgejo.org

wget https://codeberg.org/forgejo/forgejo/releases/download/v9.0.2/forgejo-9.0.2-linux-amd64
chmod +x forgejo-9.0.2-linux-amd64

Verify GPG signature

All Forgejo binaries are signed with our GPG key to verify their authenticity and guard against unwanted modification.
To validate the signature, download the signature file which ends in .asc for the binary you downloaded and use the GPG command line tool:

gpg --keyserver keys.openpgp.org --recv EB114F5E6C0DC2BCDD183550A4B61A2DC5923710
wget https://codeberg.org/forgejo/forgejo/releases/download/v9.0.2/forgejo-9.0.2-linux-amd64.asc
gpg --verify forgejo-9.0.2-linux-amd64.asc forgejo-9.0.2-linux-amd64

Container image

Forgejo provides container images for use with Docker or other containerization tools.

Install the latest release on Docker as follows:

docker pull codeberg.org/forgejo/forgejo:9.0.2

A mirror of the releases is available in case codeberg.org can not be accessed. To use it replace codeberg.org with code.forgejo.org

Upgrade from Gitea

Forgejo is no longer guaranteed to be compatible with Gitea , but upgrades should usually be possible. We'll link you some things to be aware of. Feel free to reach out if you encounter any issues.

The Forgejo and Gitea release cycles are no longer synchronized. We test upgrades from an older Gitea instance to the most recent Forgejo version automatically, and expect such upgrades to work out-of-the-box. Forgejo will perform all necessary database migrations necessary (even if you skip releases).

If your instance uses a Gitea version that is lower or equal to the advertised compatible version of Forgejo, you should follow the upgrade instructions in the Forgejo documentation, and ensure that you have a working backup! Do not upgrade Gitea, immediately upgrade to Forgejo versions.

If your instance uses a newer Gitea version than known to be compatible, you can either stop doing major Gitea upgrades and wait for the next Forgejo release, or you can run the latest Forgejo development version from source. They often lag behind Gitea database migrations only for a few days, but are not otherwise tested to be compatible.

Documentation

The Forgejo documentation is now available!
It includes an extensive user guide and admin guide to help you get started, whether you're hosting Forgejo yourself or using a public instance.