Compatibility
Arbinel is fully compatible with the Forgejo release it is built on, in both directions. This is a commitment of the project: a change that breaks it does not get merged.
From Forgejo to Arbinel
Section titled “From Forgejo to Arbinel”Replace a Forgejo release with the Arbinel release built on the same Forgejo version. The instance keeps running on its existing database, repositories, configuration and storage, and nothing needs converting. Switch from Forgejo walks through it.
From Arbinel back to Forgejo
Section titled “From Arbinel back to Forgejo”Replace an Arbinel release with the Forgejo release it is built on, and the instance keeps running. Forgejo ignores the tables and columns Arbinel added, and all data Forgejo knows about stays intact. Arbinel’s own features stop working, but their data stays in the database, and switching back to Arbinel restores them.
Later upgrades
Section titled “Later upgrades”An Arbinel instance can upgrade to any later Arbinel release, or to any later Forgejo release. Arbinel keeps its schema changes in a migration chain of its own, which only adds tables and columns. It never adds, removes or changes a migration in Forgejo’s chain, so Forgejo’s future migrations always apply to an Arbinel database.
Interfaces
Section titled “Interfaces”Forgejo’s API, configuration keys, command line, Git and SSH behaviour, and package registries work in Arbinel as they do in the Forgejo release it is built on. Arbinel adds its own endpoints, settings and options, and never removes or changes the meaning of Forgejo’s.
The API’s version endpoints and forgejo --version keep reporting the Forgejo version in Forgejo’s format.
Forgejo Runner, Renovate and other clients that check the version work against Arbinel unchanged.
The site administration summary shows both the Arbinel version and the Forgejo version it is compatible with.
Features are off by default
Section titled “Features are off by default”Arbinel’s server-side features are off by default. An instance that switches from Forgejo enforces no quota, budget or limit until you configure it.
A few interface defaults do differ from Forgejo, such as the default theme and the /inbox page.
Defaults that differ lists each of them.
Forgejo version
Section titled “Forgejo version”The release notes of each Arbinel release name the Forgejo release it is built on. That Forgejo release is the one Arbinel is compatible with and can replace. Upgrading explains how Arbinel’s version numbers relate to Forgejo’s.