Skip to content
Reoclo Docs

Gitea Integration

In addition to GitHub, Reoclo supports Gitea as a git provider. This lets you deploy from self-hosted Gitea repositories with the same webhook-driven workflow as GitHub.

How It Works

Section titled “How It Works”
  1. You register your Gitea instance as a git provider in Reoclo
  2. You authorize Reoclo via OAuth2 to access your repositories
  3. Reoclo syncs your repositories and sets up webhooks
  4. Pushing to a configured branch triggers deployments, just like GitHub

Prerequisites

Section titled “Prerequisites”
  • A Gitea instance accessible via HTTPS
  • Admin access to create an OAuth2 application on the Gitea instance
  • A Reoclo admin role in your organization

Setting Up Gitea

Section titled “Setting Up Gitea”

1. Create an OAuth2 Application in Gitea

Section titled “1. Create an OAuth2 Application in Gitea”

In your Gitea instance:

  1. Go to Site Administration > Applications (or User Settings > Applications for user-scoped)
  2. Click Create a new OAuth2 Application
  3. Fill in:
    • Application Name: Reoclo
    • Redirect URI: https://app.reoclo.com/git-providers/callback (or your self-hosted Reoclo URL)
  4. Click Create Application
  5. Copy the Client ID and Client Secret

2. Add the Git Provider in Reoclo

Section titled “2. Add the Git Provider in Reoclo”
  1. Navigate to Settings > Git Providers in the dashboard
  2. Click Add Provider
  3. Select Gitea as the provider type
  4. Fill in:
    • Name: descriptive label (e.g., “Company Gitea”)
    • Instance URL: your Gitea instance URL (e.g., https://git.company.com)
    • OAuth Client ID: from step 1
    • OAuth Client Secret: from step 1 (encrypted at rest)
  5. Click Create

3. Connect via OAuth

Section titled “3. Connect via OAuth”
  1. On the provider detail page, click Connect
  2. You’ll be redirected to your Gitea instance for authorization
  3. Authorize Reoclo to access your repositories
  4. You’ll be redirected back to Reoclo

Once connected, Reoclo automatically syncs your repositories.

4. Filter by Organization (Optional)

Section titled “4. Filter by Organization (Optional)”

If you only want repositories from specific organizations, set Allowed Organizations on the provider. Only repositories from those organizations will be synced.

Repository Sync

Section titled “Repository Sync”

After connecting, Reoclo fetches all repositories you have access to. The sync:

  • Runs automatically after OAuth connection
  • Can be triggered manually from the provider detail page
  • Shows progress (total repos, completed repos)
  • Handles pagination for large accounts

Synced repositories appear when creating applications, just like GitHub repositories.

Webhooks

Section titled “Webhooks”

Reoclo automatically configures webhooks on your Gitea repositories when you create an application. Push events trigger deployments the same way GitHub push events do.

Each provider has a unique webhook secret generated automatically for signature verification.

Differences from GitHub

Section titled “Differences from GitHub”
FeatureGitHubGitea
SetupPlatform-managed GitHub AppPer-organisation OAuth2
ScopeOrganization-wide via App installUser-level via OAuth token
WebhooksAutomatic via GitHub AppAutomatic via Reoclo
Token managementShort-lived installation tokensOAuth refresh tokens (rotated on use)
PR previewsSupportedNot yet supported

Troubleshooting

Section titled “Troubleshooting”
IssueCauseFix
OAuth redirect failsWrong redirect URI in Gitea appVerify the redirect URI matches your Reoclo instance
No repositories after connectToken lacks permissionsRe-authorize with a user that has access to the repos
Sync shows 0 reposAllowed organizations filter too restrictiveClear the org filter or add the correct organizations
Webhooks not triggeringGitea can’t reach ReocloEnsure your Gitea instance can make outbound HTTPS to Reoclo

Next Steps

Section titled “Next Steps”