Connect Gitea or Forgejo

ReaperCI supports hosted or self-hosted Gitea and Forgejo without moving the canonical repository.

1. Confirm the ReaperCI hub and forge can reach each other over HTTPS. Avoid an IP address when certificates are issued for a DNS name.
2. Create a dedicated forge user or service identity and an expiring token with access only to the repositories being adopted. It needs repository read, webhook administration, and commit-status access.
3. In Repos > Sources, choose Gitea or Forgejo, enter the forge origin URL, token-owner username, and token.
4. Test, discover, and import the repository. Verify the displayed clone URL and signed webhook target before marking the old CI path inactive.
5. Push a migration branch containing .reaperci.yml, inspect the mirror sync delivery, and confirm the provider commit status links back to the ReaperCI build.

For a forge reachable only through a private network, place ReaperCI on that network or use an operator-controlled route. Do not disable TLS verification to work around a certificate-name or trust problem; install the appropriate CA and use the matching hostname.

If an automatic webhook cannot be created, use the one-time secret shown by ReaperCI to install the exact callback manually, then refresh the source. A mirror that is not ready must not be treated as current source code.