We're excited to announce the official launch of the #Forgejo project, a community-driven fork of #Gitea under the stewardship of @Codeberg.

Check out forgejo.org/2022-12-15-hello-f… to learn more, including the motivation for the fork, as well as Codeberg's announcement at blog.codeberg.org/codeberg-lau…

Come and get involved at codeberg.org/forgejo/forgejo or in our Matrix room matrix.to/#/#forgejo-chat:matr… . We aim to be a fully inclusive community and everyone's participation is welcomed.

in reply to Forgejo

@dachary I don't think I'll have much time to do real testing. On my end, it's indeed running on a BananaPi with Armbian, mostly mirroring my repos from different places but also being primary for my local stuff (configurations etc), so it would be bad if it "breaks things". But if the worst thing should "usually" be that the binary isn't starting up, or anything else that could be fixed by just replacing it with the previous Gitea, why not.
in reply to Pádraic - Slovene Era

@padraic @IzzyOnDroid actually... the 1.18.0 will also include armv6/armv7 binaries if they can be automatically tested with qemu in the CI, which is likely.

An issue was created to track this work.

codeberg.org/forgejo/forgejo/i…

~ @dachary

in reply to Forgejo

@padraic @IzzyOnDroid @dachary Forgejo 1.18.0 will provide armv6 binaries. Those can also be used on armv7.

The Forgejo release process will include the generation of arm-6 binaries and a qemu based test that verifies it is functional.

If you are curious about how it is done checkout this (very short) pull request.

codeberg.org/forgejo/forgejo/p…

~ @dachary