Forgejo

App in the BluixApps catalog

What it is

Forgejo is a community-driven fork of Gitea — a lightweight, self-hosted Git platform with code hosting, issue tracking, PRs, CI/CD via Forgejo Actions, container registry. Started in 2022 when Gitea pivoted toward commercial ownership; Forgejo is now Codeberg's preferred platform and the truly community-owned option.

For teams who want Git hosting without trusting commercial roadmap pressure.

What it's for

  • Self-hosted Git — code hosting for internal / private projects
  • Issue tracking — GitHub Issues equivalent
  • Pull request workflow — code review on your infrastructure
  • CI/CD with Forgejo Actions — GitHub Actions-compatible workflow runner
  • Container registry — push Docker images privately

Who it's for

  • Engineering teams wanting self-hosted Git for proprietary code
  • Open-source projects moving from GitHub (often due to Microsoft concerns)
  • Privacy-bound orgs keeping code in-network
  • Cost-conscious teams avoiding GitHub Enterprise per-seat billing
  • Communities building shared infrastructure (Codeberg model)

Why teams pick Forgejo over alternatives

  • MIT license + community governance — fork of Gitea with explicit community ownership
  • Lightweight — runs comfortably on $5/mo VPS
  • GitHub Actions compatibility — most existing workflows work with Forgejo Actions
  • Active development — strong release cadence by maintainer collective
  • Federation — early support for ActivityPub-based federation
  • No commercial conflict — explicitly non-profit governance

Integrations

  • Git protocols — SSH, HTTPS, git daemon
  • Authentication — local + LDAP + OAuth (GitHub, GitLab, custom) + SAML
  • Webhooks — fire on push / PR / issue events
  • Actions runners — Forgejo Actions for GitHub-compatible CI/CD
  • Container registry — OCI registry built-in
  • Package registry — npm, PyPI, Maven, NuGet, Composer
  • Mirror — push/pull mirror to GitHub, GitLab, Codeberg

Notable users & community

  • 4k+ GitHub stars (rapidly growing)
  • Codeberg uses Forgejo as primary platform
  • Many OSS projects migrating from Gitea or GitHub
  • Active matrix.org community
  • Backed by Codeberg e.V. (non-profit) — strong governance

Tips & operations

  • Choose carefully between Forgejo and Gitea — Forgejo for community governance, Gitea for commercial-backed
  • Set SECRET_KEY in env — auto-generated but should be preserved across upgrades
  • Use Postgres for production — default SQLite breaks under multi-user concurrent writes
  • SSH server config — Forgejo can run its own SSH or use system SSH; pick one
  • Backup is critical — DB + repo files + attachments + LFS = three separate stores
  • Federation is alpha — useful for personal but not production-ready

What we ship in BluixApps

  • Docker compose: Forgejo + Postgres
  • Pinned codeberg.org/forgejo/forgejo:11.0 (release-tagged LTS)
  • HTTPS via Let's Encrypt
  • Admin user via first-run wizard
  • Persistent volumes for repos + database + attachments
  • SSH server enabled on alternate port
  • Backup hook covers Postgres + repo files + attachments
Read this app's deep dive on bluix.app ↗

Get this app — pick a BluixApps plan

Same catalog. Scaling tenant isolation, white-label and support tier.

TierTenantsCatalogSupportWhite-labelMonthly
Stacks119 curated stacksStandard$19/moDetailDeploy
Starter10Full catalogStandard+$15–25/mo$49/moDetailDeploy
Pro25Full catalogPriority bugfix+$15–25/mo$149/moDetailDeploy
Growth100Full catalogPriority bugfix+$15–25/mo$349/moDetailDeploy
Scale500Full catalog7-day window+$15–25/mo$799/moDetailDeploy
EnterpriseUnlimitedFull catalogPriority 7-dayBundled$1,499/moDetailDeploy

Powered by WHMCompleteSolution