Forgejo v14.0 is available
90 points by FedericoSchonborn
90 points by FedericoSchonborn
I love how making things work without JavaScript is given weight.
I'm working on bare Git hosting without a forge, but I really like where Forgejo is going.
I just updated from 13 to 14, with a total downtime of about 30 seconds. I love it when a major version upgrade goes so smooth. I even ran the doctor commit-status-cleanup step, which removed a whole 91 records (out of 28.6k).
Uneventful upgrades are the best, and this is yet another one for me.
10 seconds of downtime here! It's nice to see that good software is still out there, despite everything.
I just started running Forgejo in my homelab alongside Tailscale which I manage using Terraform. The whole thing feels like magic.
I never realised how slow GitHub was. Pushing code to Forgejo is instant. It’s not just the latency.
Wonder what it would take to get the Linux Foundation (or similar) to run its own ForgeJo instance for the projects operating under it. Especially once cross-instance PRs from codeberg users become viable.
I couldn't find this anywhere, but how much has Forgejo diverged from Gitea at this point? EDIT: Forgejo's own docs just say read the release notes and mind-diff them, FWIW.
Is there anyone offering it hosted and supported as a service?
Codeberg is hosted forgejo
It excludes proprietary/commerical development (if maybe not in practice, at least in spirit).
So if you want hosted private Forgejo for commercial development, you just go with gitea?
I am also bumped by this. Hopefully someone will step up to offer a paid Forgejo service for commercial projects. Currently self hosting is the only option (and I am very satisfied with it).
I also searched for this a while ago and couldn't find for any of the two (Forgejo or Gitea). Is there any hosted Gitea instance that a person could host private/paid repositories? I could only find offerings that host an instance for you.
I’m actually trying to build one as a side project but it’s a pretty big lift. I don’t wanna burn myself out on it by offering it for free but I don’t wanna charge anyone for it until it’s actually good. maybe one day, but definitely not soon.
Is there anyone offering it hosted and supported as a service?
I'm using https://www.pikapods.com/ for this. But beware that there are some limitations, like you cannot push via SSH (so i'm using the git-credential-oauth helper instead). I've also not yet tried to use/configure CI runners, i don't even know if it will be possible.
I have attempted to launch a project on Codeberg, and the documentation related to this is in complete shambles. Nobody really knows, seems to be the upshot. Anything that is documented might be out of date or wrong.
Can you elaborate? It’s pretty close to everything else imo
The CI story on Codeberg is an absolute nightmare. They implemented their own private Woodpecker, which:
But since Gitea added act support for GitHub actions, Forgejo followed suit. So now there's two CI systems. But you're dealing with a fork of a platform using an open-source clone, so how to actually use it is not very clear.
The forgejo-runner is somehow a worse experience than githun actions, all of the downsides with the added benefit of not being fully compatible and as correctly implemented.
I'm going back to woodpecker when I can find the time.
For Zig, the Forgejo Runner has been an upgrade in literally every aspect I can think of. It's faster, more reliable, more observable, more portable, has a better UI, etc.
I guess I can see how you might find it worse if you approach it strictly from the perspective of needing it to be 100% compatible with GitHub Actions, but for us, it wasn't a big deal to make the couple of minor adjustments needed to deal with the differences, considering all the other benefits we got.
this inevitable when attempting to mimic GH actions, the implementors will always be playing catchup with upstream releases. it would be best to simply leave GHA altogether.
Having dealt with a bit of github actions, gitlab pipelines and codeberg's woodpecker, I did not find it worse than the two former ones. They all have similar friction points, most notably the debug/retry loop is annoying. I've also used sourcehut builds, which allow you to SSH into failed jobs, which is very nice. They have other drawbacks though (very minimalist).
has an undocumented internal linkage to a specific user account only works when that undocumented user clicks the button
I don't understand this part? I requested access for my user and my org, it was accepted, it just works and I never had to click that "repair repo" button.
I've also used sourcehut builds, which allow you to SSH into failed jobs
I cannot for the life of me understand why nobody else offers this. Across GitHub, Gitlab, Codeberg/Forgejo and Jenkins, I literally have to insert debug shell commands into the right place and run the whole job again and hope the commands surface anything relevant. Why does none of the major players in the space seem to think that inspecting why a job failed is useful?? It wastes so much time to re-run the same 10 minute job )if I'm lucky!) again and again to slowly figure out what's going on. Wastes their compute resources too.
I don't understand this part? I requested access for my user and my org, it was accepted, it just works and I never had to click that "repair repo" button.
If you don't happen to run a job for some unspecified amount of time, Woodpecker will simply stop responding to your repo. You can only fix this by going into settings -> Actions -> Repair Repository.
But only the user that created the integration is allowed to do this. Other authorized users in your Org cannot.
There is no documentation on this, and filing issues asking for help does no good. I had to figure this out through trial and error.
I think what that repair repo button does is just set up the webhook in the repo settings "linking" forgejo and woodpecker. I did not know it expired after some inactivity.
Is there anyone offering it hosted and supported as a service?
https://codeberg.org/forgejo/professional-services/issues?state=open&labels=189709
I have had a lot of fun deploying my own foregjo instance this week, along with a devpi mirror. I'm trying to slowly disentangle myself from github. Microsoft has taken its toll. I found installing and operating forgejo via homebrew to be very pleasant.