Connect GitLab, Bitbucket, or Gitea

strackt deploys from more than GitHub. Connect GitLab, Bitbucket Cloud, Gitea, or a self-hosted GitLab, and every application in your workspace can pick a repository from that account — with the same browse, detect, and deploy-on-push experience.

GitLab and Bitbucket: connect with one click

Open Settings → Source control and choose Connect GitLab or Connect Bitbucket. The provider asks you to approve access, then sends you back to strackt with your account connected. You do this once per workspace.

Gitea and self-hosted GitLab: connect with a token

For Gitea or a GitLab instance you host yourself, choose the provider card and enter two things:

• Instance URL — where your Git host lives, like https://git.example.com.
• Access token — a personal access token from your account there. For GitLab, the token needs the api scope; for Gitea, it needs repository write access.

strackt checks the connection before saving, and the token is stored encrypted.

One thing to know: your Git host must be reachable from the internet for push-to-deploy to work. If it isn't, you can still deploy — you'll just trigger deploys from strackt instead of on push.

What strackt sets up for you

When you link a repository to an application, strackt adds a webhook to that repository for you, so pushes reach strackt without any manual setup. Unlink the repository (or delete the application) and strackt removes the webhook again.

Deploys pull your code over a secure connection using short-lived access where the provider supports it. Your token is never written into your repository or your server's configuration.

Deploy automatically on push

Exactly like GitHub: turn on auto-deploy and every push to the branch your application tracks deploys it. Pushes to other branches do nothing.

If your connection stops working

Tokens expire and access gets revoked. When strackt can no longer reach your account, the provider shows Needs reconnect on the Source control settings page. Reconnect (or paste a fresh token) and everything resumes — your linked repositories stay in place.

What to do next

• Ready to add an application from a connected repository? See Add and deploy an application.
• Deploying from GitHub instead? See Connect GitHub.