<![CDATA[Forgejo]]>Forgejo is a self-hosted lightweight software forge.
Easy to install and low maintenance, it just does the job.

Brought to you by an inclusive community under the umbrella of Codeberg e.V., a democratic non-profit organization, Forgejo can be trusted to be exclusively Free Software. It includes and cooperates with hundreds of projects (Gitea, Git, ...) and is focused on scaling, federation and privacy.

Website: https://forgejo.org
Docker: https://forgejo.org/download/

]]>https://forum.cloudron.io/topic/9764/forgejoRSS for NodeSat, 13 Jun 2026 03:16:40 GMTSat, 05 Aug 2023 07:14:45 GMT60<![CDATA[Reply to Forgejo on Wed, 28 Jan 2026 11:31:35 GMT]]>Well done timconsidine! Great stuff nebulon!

]]>https://forum.cloudron.io/post/119291https://forum.cloudron.io/post/119291Wed, 28 Jan 2026 11:31:35 GMT<![CDATA[Reply to Forgejo on Tue, 27 Jan 2026 20:06:08 GMT]]>Locking this thread. The package is out and the forum category is at https://forum.cloudron.io/category/216/forgejo

]]>https://forum.cloudron.io/post/119258https://forum.cloudron.io/post/119258Tue, 27 Jan 2026 20:06:08 GMT<![CDATA[Reply to Forgejo on Mon, 26 Jan 2026 14:31:06 GMT]]>@girish great ! hope my package was helpful start

]]>https://forum.cloudron.io/post/119169https://forum.cloudron.io/post/119169Mon, 26 Jan 2026 14:31:06 GMT<![CDATA[Reply to Forgejo on Mon, 26 Jan 2026 14:28:18 GMT]]>@timconsidine I am taking it forward here https://git.cloudron.io/packages/forgejo-app

]]>https://forum.cloudron.io/post/119168https://forum.cloudron.io/post/119168Mon, 26 Jan 2026 14:28:18 GMT<![CDATA[Reply to Forgejo on Mon, 26 Jan 2026 12:22:31 GMT]]>@girish

  • I have pushed a commit to git.cloudron.io (it was my IDE git setup only pushing to one repo and I was too dozey to notice)
  • tested git clone ssh://git@git.cloudron.io:6000/xxx/xxx from a repo on my git.cloudron.io to a temp directory : no password prompt, tested clone success by ls of temp directory
  • did not try ssh git push but I assumed it will work if the git clone ssh://git@git.cloudron.io:6000/xxx/xxx worked
]]>https://forum.cloudron.io/post/119165https://forum.cloudron.io/post/119165Mon, 26 Jan 2026 12:22:31 GMT<![CDATA[Reply to Forgejo on Mon, 26 Jan 2026 11:02:52 GMT]]>@girish hmmm, seems my commit / push is not working fully. It's probably a gremlin here because I push to my private repo and also to git.cloudron.io.

Investigating ...

]]>https://forum.cloudron.io/post/119164https://forum.cloudron.io/post/119164Mon, 26 Jan 2026 11:02:52 GMT<![CDATA[Reply to Forgejo on Mon, 26 Jan 2026 10:42:39 GMT]]>@timconsidine awesome! setup_admin is missing, maybe you forgot to push? In bash, you can do set -eu at the top and this will make missing things error properly. git clone via ssh also doesn't work but I can debug that once you have pushed everything.

]]>https://forum.cloudron.io/post/119162https://forum.cloudron.io/post/119162Mon, 26 Jan 2026 10:42:39 GMT<![CDATA[Reply to Forgejo on Sun, 25 Jan 2026 15:14:16 GMT]]>@girish I have made changes :

SSH :

  • Manifest : Added tcpPorts.SSH_PORT (default 29418) to CloudronManifest.json . This tells Cloudron to open the firewall.
  • Start Script : Configured SSH_PORT and SSH_LISTEN_PORT in start.sh to match the manifest.

OIDC (SSO) :

  • Manifest : Added oidc addon to CloudronManifest.json .
  • Start Script : Added setup_oidc function in start.sh which injects the OIDC configuration directly into the database ( login_source table) and enables OIDC in app.ini .

Admin User :

  • Start Script : Added setup_admin function in start.sh . It checks if the user count is 0, and if so, creates a default admin user with a known password.

SMTP (Email) :

  • Manifest : Added sendmail addon to CloudronManifest.json .
  • Start Script : Configured [mailer] section in app.ini using Cloudron's environment variables ( CLOUDRON_MAIL_SMTP_SERVER , etc.).

Pushed v1.0.1 to git.cloudron.io/timconsidine/cloudron-forgejo

Once less job for you @girish, or hopefully less for you to fix 😄

]]>https://forum.cloudron.io/post/119132https://forum.cloudron.io/post/119132Sun, 25 Jan 2026 15:14:16 GMT<![CDATA[Reply to Forgejo on Sun, 25 Jan 2026 11:01:24 GMT]]>@girish thank you

I was not aware - I thought they were in sync - was probably rushing too much or jumping to conclusions. Will look into it. You will do a better job, I'm sure, but I will see if I can manage it - good experience (hopefully).

]]>https://forum.cloudron.io/post/119126https://forum.cloudron.io/post/119126Sun, 25 Jan 2026 11:01:24 GMT<![CDATA[Reply to Forgejo on Sun, 25 Jan 2026 10:59:29 GMT]]>@timconsidine sorry, wasn't clear. What I meant is the package has to be updated to support the various things (which are in the gitea package already):

Probably missing others... but my note was generally to get the package in sync with gitea one. AFAIK gitea and forgejo deploy very similarly since they only recently forked.

I can do this tomorrow as well but wanted to leave a note in case you wanted to do it.

]]>https://forum.cloudron.io/post/119125https://forum.cloudron.io/post/119125Sun, 25 Jan 2026 10:59:29 GMT<![CDATA[Reply to Forgejo on Sun, 25 Jan 2026 10:40:32 GMT]]>@girish my deployed Forgejo is reporting :

Powered by Forgejo Version: 14.0.1+gitea-1.22.0

I read this as meaning it is already pulling in Gitea features ... or actually it's not pulling the Gitea features you mentioned ?

EDIT :. my AI says features available but I need to improve my package

]]>https://forum.cloudron.io/post/119121https://forum.cloudron.io/post/119121Sun, 25 Jan 2026 10:40:32 GMT<![CDATA[Reply to Forgejo on Sun, 25 Jan 2026 10:00:07 GMT]]>push of LICENCE to git was skipped - bizarre - force pushed now

investigating other comments

]]>https://forum.cloudron.io/post/119120https://forum.cloudron.io/post/119120Sun, 25 Jan 2026 10:00:07 GMT<![CDATA[Reply to Forgejo on Sun, 25 Jan 2026 09:18:08 GMT]]>Strange, let me look into it.

]]>https://forum.cloudron.io/post/119118https://forum.cloudron.io/post/119118Sun, 25 Jan 2026 09:18:08 GMT<![CDATA[Reply to Forgejo on Sun, 25 Jan 2026 08:56:40 GMT]]>I think LICENSE file change was may be not pushed.

I am thinking we should keep the gitea package and forgejo package mostly in sync. The current forgejo package misses openssh server+exposing the port, creating default admin user, oidc integration, email etc. Maybe all these bits can be copied from the gitea package (which in turn copied from gogs package).

]]>https://forum.cloudron.io/post/119117https://forum.cloudron.io/post/119117Sun, 25 Jan 2026 08:56:40 GMT<![CDATA[Reply to Forgejo on Sat, 24 Jan 2026 11:35:52 GMT]]>@timconsidine

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.

]]>https://forum.cloudron.io/post/119082https://forum.cloudron.io/post/119082Sat, 24 Jan 2026 11:35:52 GMT<![CDATA[Reply to Forgejo on Sat, 24 Jan 2026 11:30:57 GMT]]>LICENSE added, in sync with Forgejo

]]>https://forum.cloudron.io/post/119081https://forum.cloudron.io/post/119081Sat, 24 Jan 2026 11:30:57 GMT<![CDATA[Reply to Forgejo on Sat, 24 Jan 2026 10:07:30 GMT]]>@girish oops yes I will put a licence this morning

I find gitea UI a touch dated but it’s a git tool so most interactions via terminal or script, so maybe it doesn’t matter.

But Forgejo seems a touch fresher

]]>https://forum.cloudron.io/post/119078https://forum.cloudron.io/post/119078Sat, 24 Jan 2026 10:07:30 GMT<![CDATA[Reply to Forgejo on Sat, 24 Jan 2026 09:53:00 GMT]]>@timconsidine can you throw in a license? I literally just moved to gitea from gogs 😠 but maybe I will move to forgejo...

]]>https://forum.cloudron.io/post/119077https://forum.cloudron.io/post/119077Sat, 24 Jan 2026 09:53:00 GMT<![CDATA[Reply to Forgejo on Sat, 24 Jan 2026 02:31:00 GMT]]>I packaged Forgejo.
My git repo : https://git.cloudron.io/timconsidine/cloudron-forgejo

not added to CCAI catalogue yet

]]>https://forum.cloudron.io/post/119065https://forum.cloudron.io/post/119065Sat, 24 Jan 2026 02:31:00 GMT<![CDATA[Reply to Forgejo on Fri, 23 Jan 2026 17:10:43 GMT]]>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.

]]>https://forum.cloudron.io/post/119052https://forum.cloudron.io/post/119052Fri, 23 Jan 2026 17:10:43 GMT<![CDATA[Reply to Forgejo on Thu, 22 Jan 2026 15:27:19 GMT]]>@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.

https://codeberg.org/bart/forgejo-app

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 ?

]]>https://forum.cloudron.io/post/118991https://forum.cloudron.io/post/118991Thu, 22 Jan 2026 15:27:19 GMT<![CDATA[Reply to Forgejo on Mon, 13 Jan 2025 22:55:34 GMT]]>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.

]]>https://forum.cloudron.io/post/99933https://forum.cloudron.io/post/99933Mon, 13 Jan 2025 22:55:34 GMT<![CDATA[Reply to Forgejo on Mon, 06 Jan 2025 13:34:03 GMT]]>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.

]]>https://forum.cloudron.io/post/99403https://forum.cloudron.io/post/99403Mon, 06 Jan 2025 13:34:03 GMT<![CDATA[Reply to Forgejo on Thu, 19 Dec 2024 15:45:05 GMT]]>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?)

]]>https://forum.cloudron.io/post/98531https://forum.cloudron.io/post/98531Thu, 19 Dec 2024 15:45:05 GMT