GitLab

1. What you get with GitLab
2. How the integration works
3. Good to know

GitLab covers the whole DevOps lifecycle — repositories, CI/CD, issues, registry — in one application, and uniquely lets you choose where it runs: on GitLab.com or on a self-managed instance behind your own firewall. Rocketeers connects to both. Link your GitLab and your sites deploy automatically on every push, whether the repository lives in GitLab's cloud or your own server room.

#What you get with GitLab

• Automatic deployments on push, from GitLab.com or self-managed GitLab.
• Private projects, groups and protected branches fully supported.
• Deploy a different branch per environment — main to production, develop to staging.
• Your GitLab CI pipelines keep running untouched; Rocketeers handles getting code onto the server, not your builds.
• Nothing about your repository setup has to change.

#How the integration works

For GitLab.com, connect via OAuth and pick the project and branch for each site. For self-managed instances, point Rocketeers at your instance URL and authenticate with a personal access token — the instance needs to be reachable from the internet so webhooks can flow. Either way, Rocketeers registers a webhook on the project and deploys your site each time a push lands on the watched branch.

#Good to know

• Self-managed GitLab works on any recent version; the integration relies on standard GitLab APIs and webhooks rather than anything version-specific.
• Personal access tokens can be rotated without breaking your sites — just update the token in Rocketeers.
• If your CI pipeline must pass before code reaches the deploy branch, use protected branches and merge-only workflows; Rocketeers simply reacts to the push.
• GitLab.com's free tier is enough — no paid plan required to deploy private projects.