Skip to content
Arbinel

Introduction

Arbinel is a soft fork of Forgejo, the self-hosted software forge. It adds features that a public, multi-tenant forge needs and Forgejo lacks. These include usage quotas, paid add-ons, several nodes behind a load balancer and hosted static sites. Arbinel merges every Forgejo release, typically within a week.

Arbinel runs codefloe.com, the forge it was built for. codefloe.com runs the code published in arbinel/arbinel, with no private features. Only the configuration differs between codefloe.com and any other Arbinel instance.

Use Arbinel for a forge that serves people outside your own team, or for an instance that needs a feature Forgejo does not have. For a forge used by a single team that needs none of the features in Arbinel and Forgejo, Forgejo works as well. Arbinel stays compatible with Forgejo, so you can try it and go back without losing data.

Forgejo’s documentation covers everything Arbinel inherits from Forgejo, and this documentation does not repeat it. It describes:

  • Additions, such as quotas, billing, high availability and Pages.
  • Changes, such as the inbox, the default theme and a few other defaults.
  • Forgejo topics that are unclear in Forgejo’s documentation, with a short explanation of the Forgejo part and a link to Forgejo’s documentation.

For everything else, read Forgejo’s documentation for the Forgejo release your Arbinel release is built on. Configuration keys, the API, the command line, and Git and SSH work as they do in Forgejo.

Arbinel started as forgejo-codefloe, and some identifiers still carry that name. The theme family is codefloe-tide, and request budgets use [codefloe.ratelimit.*] sections. These names are part of the configuration interface and will not change.

The executable and the container entrypoint are still forgejo. As a result, you can replace Forgejo with Arbinel without changing service files, scripts or orchestration.