Git Providers
Free & Pro. Connect a Git host once under Settings → Git Providers, and every Git Deployment app can pick repos from it instead of typing a raw clone URL — with webhooks registered automatically.
GitHub — One Click, No Tokens
GitHub connects differently from the other three: DockPod creates its own GitHub App for your panel instance via GitHub's App manifest flow, rather than asking you to paste a personal access token.
Click GitHub in the Available Providers list, confirm the panel's public URL, and you're redirected to GitHub to approve the app — no scopes to pick, no token to copy or accidentally leak. Each DockPod install gets its own uniquely-named App (dockpod-<random>), since GitHub App names must be globally unique.
GitHub validates the webhook URL at manifest time and rejects localhost outright. If you're browsing the panel via localhost (common for local dev), enter a public URL GitHub can actually reach — a real domain (see Panel Domain) or a tunnel like cloudflared/ngrok pointed at the panel.
GitLab, Bitbucket, Gitea — Personal Access Token
The other three providers connect with a token you generate on the provider's own side:
| Provider | Where to create it | Required scope | Extra field |
|---|---|---|---|
| GitLab | Preferences → Access tokens | api | Instance URL (leave empty for gitlab.com) |
| Bitbucket | Personal settings → App passwords | Repositories:Read + Webhooks:Read/Write | Your Bitbucket username (not email) |
| Gitea | Settings → Applications → Generate new token | (full token) | Instance URL — required, e.g. https://git.example.com |
DockPod uses the token to list your repos/branches for the create-deployment picker, clone over HTTPS at deploy time, and register the push webhook automatically — you never see or manage the webhook yourself.
What Connecting Unlocks
Once a provider is connected, creating a Git Deployment app offers a repo picker (search/select instead of pasting a URL) and automatic webhook registration, so pushes trigger a deploy without you configuring anything on the provider's side. Git Deployment still works without connecting a provider at all — paste a raw clone URL and add the webhook manually, as described in Git Deployments → Webhooks — connecting a provider is a convenience layer on top, not a requirement.
You can disconnect a provider at any time; existing deploy apps created through it keep working (their clone credentials and webhook are already provisioned), but the repo picker won't be available for new ones until you reconnect.