Forgejo v15.0 is available
(forgejo.org)
from ikidd@lemmy.world to selfhosted@lemmy.world on 20 Apr 15:24
https://lemmy.world/post/45850637
from ikidd@lemmy.world to selfhosted@lemmy.world on 20 Apr 15:24
https://lemmy.world/post/45850637
If you’re like me, you probably need to update your image tag to this new major version. I’ll probably wait for a minor release first.
#selfhosted
threaded - newest
Forgejo’s most promising feature was federation, and unfortunately, they don’t seem to be working on that.
They do, it’s just a lot of work.
Here’s an example PR: codeberg.org/forgejo/forgejo/pulls/10380
Cool!
Oh, didn’t know Forgejo was ever intended to have federation. That’s so cool!
It’s the main reason I choose them. Can’t wait to open issues on other instances without creating an account and not everything being on GitHub.
actually it is already meged and on v16.0 milestone list
That’s brilliant news!
I know this is still just very basic federation with mutual following of users, etc. - but having a working mvp implementation of this makes me really hopeful for the stepwise introduction of more and more federation goals to come to fruition.
Federation is worked on by forgefed if I remember right.
codeberg.org/ForgeFed/ForgeFed
Finally, repository specific access tokens were added! I was missing this feature from GitHub (fine-grained access tokens) and had resorted to making service accounts that had access to a single repo. Time to clean that up :)
An amazing project. Good work devs.
Yeah… I’m gonna wait for 15.1…
Can’t wait for federation
Yeees! So much different repos i want to be able to commit and report to …
This is my prerequisite for switching from GitHub to Codeberg
I very much have my eye on that. Pretty sure that’s going to be my next self-host just because I love everything about it, not so much because I’ll need it. Pleeeease federate. I know it’s a whole lot of work, but it would be a significant net benefit to all developers worldwide who code because they like it.
Donations will help them get there faster
I know, but I’ll get on that after I find a job.
Sure, no worries. For me it was the same.
Thoughts on this versus tangled besides this being more mature? Also question, I have cloudflare serving as my ddns, I believe some settings I have configured there prevent ssh from working to my forgejo instance. Is it a security risk to allow ssh traffic properly? I have other services on the same subdomain published as well if that matters.
Edit: would Tailscale be a solution here?
Recommendation would be that you want to set up your ssh so that it only accepts publickey authentication. You also want to make sure you are not using a proxied DNS value, as CF only proxies http requests.
Personally I didn’t bother to setup ssh access as https typically works fine.
I setup ssh key access only on all my machines so that bit is ok. Maybe I’ll forgo ssh like you’re suggesting as well. I thought I had some use for it but it’s been a while since I was messing with my forgejo instance, I’ve kind of fallen back to GitHub and codeberg for a bit since I’ve been busy. I couldn’t get https cloning to work for some reason either so I neee to investigate that I guess.
Tangled seems to focus on the “social” aspect by being inherently federated using the protocol Bluesky uses.
Federation is in the works for Forgejo but it’s not a focus.
How does it compare to Gitea?
Forgejo is where the dev is happening now.
It’s a fork of Gitea with more extensive development.
Gitea is developed by a corporation. If you trust corporations not to enshittify eventually, maybe Gitea will be the exception to the rule, but I doubt it, for sufficiently long definitions of “eventually”. Forgejo was forked specifically because the governance needed to be detached from the corporation, and that wasn’t going to happen with Gitea. The community of open-source developers mostly voted with their feet. Forgejo is, in my humble opinion, going places. Gitea is not. Nothing specifically wrong with it, per se, but it doesn’t really offer a sustainable development path forward I don’t think.
I didn’t notice a difference. Maybe if you start new then go forgejo but existing gitea I see no reason to move.
Forked from gitea. The owners of the project implemented a change to the pr system where by you had the sign an agreement that the code belonged to them. This was seen as an intent to relisense at some point. Devs that wanted it to stay open moved to forgejo.
Until recently you could swap forgejo in to your gitea data, but now they are incompatible due to divergence.
Isn’t that signing thing the legal way to keep things open source? Iirc FSF had that too.
Amy Idea why there isn’t a “:latest” release?
Because you usually don’t want to do automatic upgrades across major versions. There is a “latest” equivalent for each major version release though.
Forgejo was initially a soft fork of Gitea but they knew it would very possibly become a hard fork. Using the latest tag meant your setup could break unexpectedly so I think they’d opted to not use it at all. What you want to do is use the full version “15” in this case which will keep it updated up the currently major release.
It might be OK now, but for a while there before they hard forked, you set yourself up for issues if you updated majors without being aware of breaking changes.
15.0 adds support for OIDC tokens being handed to Actions workflows compatible with GitHub Actions. I was excited to upgrade because I wanted to continue doing cosign Docker image signing, but then I found out that the Cosign transparency log doesn’t support Forgejo. Looks like I need an alternative.
My next biggest problem is the Actions workflow itself. I setup Docker in Docker, but turns out there’s a bit of work in preparing the runners to be on par with what I used on GitHub.
Otherwise, I’ve found Forgejo to be quite good and almost all my private repos are moved over.
I tried to setup Forgejo CI but was turned off by the need to have nodejs installed to do anything, even cloning the repository. Does everyone just maintain their own images?
Gitlab CI by comparison will let me you any image (e.g. basic rustc imagé) and do the orchestration by itself. So much nicer to use imo
Damn I feel like I only just upgraded to v14. Those guys develop fast.
It’s noted in the release notes that they release a new major version every 3 months.
This is the first time we’re hearing of this, what is Forgejo/ what’s it used for??
Basically self hosted Github without microslop’s bs
Ah nice! Will def keep this in mind when we eventually make a server ^^
Self hosted git server (github alt)
It’s the software that runs codeberg
Locally hosted git server (fork of Gitea)
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
4 acronyms in this thread; the most compressed thread commented on today has 15 acronyms.
[Thread #250 for this comm, first seen 21st Apr 2026, 14:00] [FAQ] [Full list] [Contact] [Source code]
I’m happily running v11 LTS - I have enough to do besides dealing with breaking changes every 3 months.
That is getting pretty far behind unless you’re leaving yourself open to go back to Gitea. I think 12 was the hard fork.
I started from zero with Forgejo, so Gitea is not a consideration. I just don’t need latest and greatest as long as security is covered. But I finally noticed that v15 is the new LTS, so that’s what I hope to run during the next couple of years.
v11 goes eol in 2 months
I genuinely don’t understand your reasoning
Well, before your response, v11 was the latest LTS release, received security patches and did all I wanted it to do. Now, I actually did look at the new release and found out that 15 is a new LTS. So, thank you! I guess it’s time to review the breaking changes and get prepared.