Forgejo
-
@LoudLemur said in Forgejo:
These are quite a lot of questions, and I will do my best to answer them to the best of my ability.
It is fantastic that you discovered Cloudron. We need more people like you. How did you find out about Cloudron? What was it that persuaded you Cloudron was a platform that you would like to support?
I discovered Cloudron a couple of years ago on r/selfhosted. I was already hosting multiple services using different deployment methods: Docker, Snap, and binaries, so I never really gave it a chance.
The problem is, since I only use open-source software, I self-host all the software I use. The applications I host are all critical infrastructure for me, and self-hosting was beginning to take up more and more hours of my day, which is hard if you already have a day job. I had less time to experiment and was losing the joy of self-hosting.
Since I discovered Cloudron a few years prior and needed to remove the burden I was experiencing, I decided to try it out. It is so much easier than what I was doing before. I bought my license the same day and have been a happy customer ever since.
What do you think might make packaging applications for Cloudron easier? For example, if there was a team of packagers with different roles and working to a monthly schedule, maybe that would have helped ease onboarding.
I've been a software developer and open-source contributor for a while, and I think one of the most important aspects of having an active community is having core developers who are as excited about your contributions as you are. Make sure the contributor is recognized for the time and effort they put in and that their opinion is respected by having them participate in the decision-making process. Having these contributors be part of some kind of Hall of Fame or team of recognized contributors seems like a good way to do this.
When specifically talking about package development, I think it needs to be easier for people to install and test packages that other developers have created.
Did it take you long from discovering Cloudron to going ahead and packaging? Maybe it was very quick, but it might have been a while till you decided to begin.
Well, I discovered Cloudron a couple of years ago and have been a customer since the beginning of last year. I was always interested in creating my own package, but this is the first time I gave it a proper go.
One more fun question: Which Cloudron supported application makes you feel good that it is there? Why do you like it?
That is a tough one, there are so many applications to choose from. I am choosing Nextcloud because my family and I have been using it for multiple years now. It is a very versatile piece of software. I previously hosted it using Snap or rented a Storage Share from Hetzner, however, the ease of hosting it using Cloudron is great.
Thank you very much indeed for taking the time to answer these questions. I hope that team Cloudron will find your replies of interest. I think they will!
We were fortunate that you decided to package an application. I think one way Cloudron could improve faster is by recognizing at an earlier stage when we have a talented developer in our midst and then offering them some encouragement or incentive to start participating. I hope Cloudron can work out a way to do this. Perhaps offering some sort of voucher in exchange for packaging to a required standard.
Perhaps Cloudron could be more direct with new users and offer a Typebot form to onboard and even task people, if they indicate they might be willing.
I also note that Cloudron let a year go by without a contribution from you. Anonymity is important and good, but if we had approached you earlier all this might have happened a year ago. There might be another developer who arrived at Cloudron today, and we won't have any packaging from them for a year because we aren't in conversation.
In my experience, there are usually a few, key sites which bring in the bulk of people. In your case, it was /r/selfhosted. I think Cloudron could investigate which are the best sites like that and try and establish an active presence there. I don't know what sort of marketing effort Cloudron has. I imagine the core team are far too busy on coding to manage these other aspects of the project, too.
Thanks for telling us your fun application. I like Nextcloud too.
-
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). -
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.
