Skip to main content

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 https://forgejo.org/2022-12-15-hello-forgejo/ to learn more, including the motivation for the fork, as well as Codeberg's announcement at https://blog.codeberg.org/codeberg-launches-forgejo.html

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

forgejo

Beyond coding. We forge. (Code of Conduct: https://codeberg.org/forgejo/code-of-conduct)
Codeberg.org
#gitea #forgejo @Codeberg.org
in reply to Forgejo

IzzyOnDroid ✅
IzzyOnDroid ✅
• •
Will you also provide ARMv6/ARMv7 binaries at your releases one day – for those currently running Gitea on e.g. BananaPis?
in reply to IzzyOnDroid ✅

Forgejo
Forgejo
• •
@IzzyOnDroid yes. There is a need for testers willing to verify the result works as intended. Would you like to be part of such a team?

~ @dachary
@Loïc Dachary @IzzyOnDroid ✅
in reply to Forgejo

IzzyOnDroid ✅
IzzyOnDroid ✅
• •
@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.
@Loïc Dachary
in reply to IzzyOnDroid ✅

Loïc Dachary
Loïc Dachary
• •
@IzzyOnDroid that's an idea. Maybe forgejo could publish untested binaries somewhere for people to try, knowing it "maybe works". In a different repository so there is no confusion: that would be valuable. It is very low effort for the current release process to do that. The key is to be very clear and not give people false hope that it is "field tested" 😃

What do you think?
@IzzyOnDroid ✅
in reply to IzzyOnDroid ✅

Loïc Dachary
Loïc Dachary
• •
@IzzyOnDroid
... and could you please tell me which Gitea binary you are currently running?

but maybe we can continue this conversation on the issue that was created to provide armv6/v7 binaries?

https://codeberg.org/forgejo/forgejo/issues/117

[CI] release armv6/armv7 binaries

Some interest was expressed for armv6/armv7 binaries * https://floss.social/@padraic@tilde.zone/109523005167529821 * https://floss.
Codeberg.org
@IzzyOnDroid ✅
in reply to Forgejo

Pádraic :blobmelt:
Pádraic :blobmelt:
• •
I love the intitiative, but I wanted to ask: Will you also add builds for e.g. linux-armv6? I run my own gitea on an OG model-B Raspberry Pi, so an armv6 binary is a must...
in reply to Pádraic :blobmelt:

Forgejo
Forgejo
• •
@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.

https://codeberg.org/forgejo/forgejo/issues/117

~ @dachary

[CI] release armv6/armv7 binaries

Some interest was expressed for armv6/armv7 binaries * https://floss.social/@padraic@tilde.zone/109523005167529821 * https://floss.
Codeberg.org
@Loïc Dachary @IzzyOnDroid ✅ @Pádraic :blobmelt:
in reply to Forgejo

Forgejo
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.

https://codeberg.org/forgejo/forgejo/pulls/118

~ @dachary

WIP: [CI] add support for armv6

Refs: https://codeberg.org/forgejo/forgejo/issues/117 * 🕙 Full CI run on tag https://forgejo-woodpecker.gna.org/dachary/forgejo/pipeline/113 * ✅ Partial CI run to create the release https://forgejo-woodpecker.gna.
Codeberg.org
@Loïc Dachary @IzzyOnDroid ✅ @Pádraic :blobmelt:
in reply to Forgejo

IzzyOnDroid ✅
IzzyOnDroid ✅
• •
@padraic @dachary That's wonderful, thanks! Until then I'll update to the latest Gitea so the setup should be ready for the drop-in replacement. I guess there are some notes on migration somewhere with things one should take care for, if any?
@Loïc Dachary @Pádraic :blobmelt:
Unknown parent

IzzyOnDroid ✅
IzzyOnDroid ✅
• •
@padraic @MarvinTheRobot @dachary I've just prepared my install for that (downloaded both 1.18). I'm still on 1.17.3 currently; will go 1.17.4 => 1.18 => forgejo ASAP. Thanks for confirming the ease of migration!
@Loïc Dachary @Marvin the Robot ✅ @Pádraic :blobmelt:
Unknown parent

Pádraic :blobmelt:
Pádraic :blobmelt:
• •
@MarvinTheRobot @IzzyOnDroid @dachary

Thanks all, just upgraded from Gitea 1.17 to 1.18 and then to Forgejo 1.18 (on arm6, natch). Working great! 💪
@Loïc Dachary @Marvin the Robot ✅ @IzzyOnDroid ✅
⇧