Forgejo
-
Thanks for the inspiration folks ! I'm developer myself and would be happy to contribute to package Cloudron apps as there are some apps I want to use and I'm not the only one, of course I never dig into the docs of how to package Cloudron apps but I'm not too scared
(I'm usually busy at SRE/DevOps and Development/Automation tasks on day2day for the last 14 years and still enjoy it).@MorganGeek said in Forgejo:
SRE/DevOps
DevOps stands for Development Operations, and SRE stands for Site Reliability Engineering.
Excellent! I am keen to hear what sort of apps you might like to package. Do tell! It is quite exciting to hear.
Maybe there some other developers lurking who might like to try, too!
-
I moved from Gitea to Forgejo some time ago (https://www.tobru.ch/migrating-from-gitea-to-forgejo/) and don't look back. It would be fantastic to see Forgejo in Cloudron (maybe even move from Gitea to Forgejo so that not both have to be maintained?)
-
I have done a drop in replacement using the gitea package. You can find the build here https://github.com/campbellmcgregor/clourdon-forgejo
It is running on my cloudron so far no issues, if there any let me know and I can have a look and see where the issue lies.
-
I'm thrilled to see progress on getting Forgejo packaged. It's an exciting project, and with Fedora switching to it for their Git, it's only going to get better.
-
@ruihildt I found some time, and was able to create a working package based on the Gitea package. The source code can be found on my Codeberg profile.
https://codeberg.org/bart/forgejo-app
This is my first Cloudron package, so let me know if there's anything I can improve.
@bartmathijssen said in Forgejo:
@ruihildt I found some time, and was able to create a working package based on the Gitea package. The source code can be found on my Codeberg profile.
I tried to take a look but got 404'ed.
The page you are trying to reach either does not exist, has been removed or you are not authorized to view it.Is there a different place ? Or private ?
-
Gogs vs Gitea vs Forgejo: Which Self-Hosted Git to Pick in 2026? Dev Effort Breakdown
Tired of GitHub's censorship and bloat? Here's a no-BS comparison of the lightweight Git alternatives. All Go-based, MIT-licensed, one-binary deploys. Gogs is dead; pick Gitea or Forgejo for active dev.
Aspect Gogs (0.13.0, 2021) Gitea (1.22+, Jan 2026) Forgejo (8.0+, Jan 2026) Status Dead/abandoned (last commit 2016) Thriving (commercial/community hybrid) Active fork of Gitea (community/non-profit) Dev Effort Zero. Archived on GitHub. No security patches, vulns piling up. Fork it yourself if needed. High: 2k+ commits/month, 200+ contributors. Monthly releases, enterprise features. Backed by Gitea Ltd (Taiwan-based, less woke drama). GitHub stars: 40k+. Medium-High: 500+ commits/month, syncs Gitea upstream. 50+ core devs. Codeberg-hosted, but slower than Gitea on edge features. Stars: 10k+. Performance Ultra-light (RPi-friendly) Excellent, scales to 10k+ repos/users Matches Gitea, Docker-optimized Features Basic Git + issues/hooks Full: Actions (CI/CD), packages, wiki, LFS, federation, OAuth Same as Gitea + P2P federation emphasis Community/Woke None (based by default) Neutral-ish; CoC exists but pragmatic Woke-leaning (CoC, pronouns, censorship vibes via Codeberg) Security Unpatched (avoid prod) Frequent audits/fixes Inherits Gitea + own patches Setup/Migration Simple but manual Easiest: Docker, ARM64, Gogs importer Docker-heavy, good Gitea/Gogs tools Pros Dead simple, zero deps Feature-complete, reliable, active Decentralized governance, FOSS purist Cons No modern features/support Corporate shift irks purists Fork drama, trails Gitea dev speed Recommendations:
- Solo/based user: Gitea. Most bang-for-buck, ignore upstream politics.
- FOSS maximalist: Forgejo if you buy the anti-corp narrative (but watch the wokeness).
- Legacy: Gogs only for air-gapped hobby—migrate ASAP.
Dev metrics from GitHub/Codeberg dashboards (as of Jan 2026). Gitea wins on momentum; Forgejo if you hate companies.
-
I packaged Forgejo.
My git repo : https://git.cloudron.io/timconsidine/cloudron-forgejonot added to CCAI catalogue yet
-
@timconsidine can you throw in a license? I literally just moved to gitea from gogs
but maybe I will move to forgejo... -
LICENSE added, in sync with Forgejo
-
I packaged Forgejo.
My git repo : https://git.cloudron.io/timconsidine/cloudron-forgejonot added to CCAI catalogue yet
Well done, Tim! Excellent work.
I used to think being on Gogs was leading edge. I think I shall have to try moving over to Forgejo like girish.