If you go to their release page, you will see two versions listed. The current stable release (13.0) and the explicitlly marked LTS version (11), both with clearly visible end of support dates. Not sure how much simpler it can get :)
But I've since learned that they are in fact using SemVer which means it was my expectations of what the project was trying to do that was mismatched. I didn't expect Major updates to mirror a quarterly cadence.
No AI, EU based, so respects the GDPR for all users, regardless of where they live, you can send PRs to make it better, is 100% Free Software, has its own Actions system that is also 100% Free Software, the logo is nice, you can become a member of the Berlin based association and have a direct vote on policy/feature changes.
No. Both MacOS and iOS happily resolve and connect to the machines in my homelab.jhw domain. I did add the root cert of my CA (Certificate Authority) to the trust store on MacOS and iOS, so I can also enjoy TLS connections. Scroll to the "Add the certificate" part of https://jan.wildeboer.net/2025/08/Create-SMIME-Cert-stepca/ for the HOWTO that worked for me.
Author here. I used the homelab.jhw mainly as part of my tests and experiments with my own certificate authority and to avoid going into split horizon DNS setup.
I did this as well. I have terraform interconnected so that I make TF entries in my Unifi repo which become DHCP reservations, and the AWS terraform makes DNS records for them.
Sure. Constructing the case to shoot yourself in the foot is not a big problem. But in reality things mostly just work. I’m happily running a bunch of services behind a (nginx) reverse proxy as rootless containers. Forgejo, the forgejo runner to build stuff, uptime-kuma and more on a bunch of RHEL10 machines with SELinux enabled.
People having trouble getting this configured is a common issue for self-hosting Forgejo Runner. As a Forgejo contributor, I'm currently polishing up new documentation to try to support people with configuring this; here's the draft page: https://forgejo.codeberg.page/@docs_pull_1421/docs/next/admi...
Thanks. Maybe I'll do it the next time. That seems like less friction than having to write our representative / admim however you call the people that could add me to our subscription. But why do you put it behind that if it's free anyway?
Thank you for the clarification! That's what I thought, but then I found a bunch of comments indicating they had changed it. Glad to hear it's still free
FYI: Just last Friday there was a call/meeting to coordinate and build out the federation efforts in Forgejo. More work is coming and more help is appreciated! There will be a presentation at FOSDEM on this topic and there is a matrix room dedicated to Forgejo Federation.
After my struggles with trying to keep Gitlab CE (Community Edition) up and running (it needs a lot of CPU and memory) I switched to Forgejo and have not been disappointed. It runs as a rootless container and uses almost nothing, memory and CPU wise. Updating it has been a simple podman pull that JustWorks(tm).
It now also runs actions that keep my static websites updated by running Jekyll etc.
I really like it to have my own forge that can import repos, issues etc from other forges like GitHub, Gitlab etc. and I am looking forward to the upcoming ActivityPub based integration to the wider fediverse.
Having a decentralised, but connected approach to code hosting is what I always wanted to have and now it’s (almost) there.
