Introduction
Arbinel is a soft fork of Forgejo, the self-hosted software forge. It adds what a public, multi-tenant forge needs beyond Forgejo, such as usage quotas, paid add-ons, several nodes behind a load balancer and hosted static sites. It 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 cases
Section titled “Use cases”Arbinel suits a forge that serves people outside your own team, or an instance that needs one of the features Forgejo does not have. For a forge used by a single team that needs none of the features in Arbinel and Forgejo, Forgejo serves as well. Arbinel stays compatible with Forgejo, so you can try it and go back without losing data.
Scope of these docs
Section titled “Scope of these docs”Forgejo’s documentation covers everything Arbinel inherits, and these docs do not repeat it. They cover:
- 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 hard to follow upstream, 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.
Former name in identifiers
Section titled “Former name in identifiers”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.
They are part of the configuration interface and do not change.
The executable and the container entrypoint are still forgejo.
Arbinel therefore replaces Forgejo without changes to service files, scripts or orchestration.
Support
Section titled “Support”- Report bugs and request features in the issue tracker.
- Report security vulnerabilities in Arbinel’s own code privately to security@arbinel.com. For vulnerabilities in Forgejo’s code, follow Forgejo’s security policy.
- Report bugs that also occur in Forgejo to Forgejo, so every Forgejo user gets the fix.