Skip to content
OrbixPanel OrbixPanel Tutorials

Connect GitHub, GitLab or Bitbucket (one-click deploy)

Instead of pasting a repository URL and a personal access token every time, OrbixPanel lets you connect your Git provider once and then pick a repository and deploy — the way the big platforms do it. It works with GitHub, GitLab, and Bitbucket.

Because OrbixPanel is self-hosted, you register a provider OAuth app once (a 5-minute, one-time setup). After that, connecting and deploying is one-click, and your credentials and tokens stay encrypted on your own server — nothing goes through a third party.

Who sets this up: the server admin/owner (or the reseller in reseller mode). Tenants don’t register apps.

One-time setup: register an OAuth app

Open the page in the panel: left sidebar → App Deployment → Git Integrations (admin only), or go straight to https://<your-panel>/git-integrations. Each provider card shows the exact callback (redirect) URL to register — copy it, you’ll need it below — plus the Client ID / Secret fields you’ll fill in after registering.

Don’t see “Git Integrations” in the sidebar? The menu item ships in the web frontend — rebuild orbixpanel-web on the panel server and hard-refresh.

GitHub

  1. GitHub → Settings → Developer settings → OAuth Apps → New OAuth App.
  2. Redirect URI (GitHub’s newer label; older UIs say Authorization callback URL): paste the one from the panel (https://<your-panel>/api/git/callback/github) — exactly as the card shows it.
  3. Leave “Expire user access tokens” unchecked — OrbixPanel uses GitHub’s standard non-expiring token and doesn’t use GitHub’s refresh flow, so an expiring token would stop working after ~8 hours.
  4. Create it, copy the Client ID, generate a Client secret.
  5. Back in OrbixPanel (App Deployment → Git Integrations), paste the Client ID + secret into the GitHub card and Save.

GitLab

  1. GitLab → Preferences → Applications → Add new application.
  2. Redirect URI: the panel’s callback URL for GitLab.
  3. Scopes: read_api and read_repository. Save.
  4. Paste the Application ID + Secret into the GitLab card. (For self-hosted GitLab, also set the Base URL.)

Bitbucket

  1. Bitbucket → Workspace settings → OAuth consumers → Add consumer.
  2. Callback URL: the panel’s callback URL for Bitbucket.
  3. Permissions: Repositories: Read (and Account: Read). Save.
  4. Paste the Key + Secret into the Bitbucket card.

Connect and deploy

  1. On the provider’s card, click Connect — you’re sent to the provider to authorize, then back to OrbixPanel.
  2. Click Show my repositories — your repos appear.
  3. Pick a repo, choose a branch, and click Deploy.

OrbixPanel clones it (using the connection — no token to paste), auto-detects the runtime, builds, and serves it behind automatic SSL, exactly like a manual Git deploy. For how the build/serve works per runtime, see How deploys work.

Prefer to paste a URL?

The manual path still works — Deploy from Git and private repos with a token. Connecting a provider just removes the copy-paste.

Security notes

  • The OAuth app secret and the access tokens are encrypted at rest on your server.
  • GitLab/Bitbucket tokens are refreshed automatically when they expire.
  • Disconnect any time from the provider’s card — it removes the stored tokens.

Running OrbixPanel? Connect once, then deploy any repo in a couple of clicks. OrbixPanel.com → — the free, self-hosted, AI-powered hosting control panel.