Self-Hosted GitLab

Codeac supports self-hosted Git repositories for the GitLab Community Edition.

Exposing Ports

To use your private GitLab server with Codeac, you will need a publicly reachable endpoint with ports 22 and 443 open to the internet. We require port 22 to clone your repository to run our analysis and port 443 for status and clone requests.

To check that these ports are open you can run the following against your server from your local machine:

CLI

nc -v -w1 mygitlabserver.com 22
# => Connection to mygitlabserver.com 22 port [tcp/ssh] succeeded!

nc -v -w1 mygitlabserver.com 443
# => Connection to mygitlabserver.com 443 port [tcp/https] succeeded!

Personal Access Tokens

To connect to your self-hosted GitLab instance, you will need to retrieve your personal access token. To fetch your token, follow these instructions:

Token Access Scopes

In order for Codeac to be allowed to setup the necessary hooks etc. the personal access tokens need to have the correct set of scopes. Below you’ll find the necessary setting for self-hosted GitLab server:

GitLab Settings

Copy the redirect URL into your GitLab Application settings.

Redirect URL

https://api.codeac.io/v1/auth/gitlab/callback

To get your self-hosted GitLab instance up and running with Codeac, there are still a few manual steps on our side needed. Please contact us at support@codeac.io and we will help you with the on-boarding.

SCM Feature Request

We are continually evaluating our SCM integration support. If there is something you would like to see, please get in touch and let us know more details about your SCM needs.

Security

To read more about our security setup, please review our security documentation or ask us a question.