How to use GitLab repository manager to manage your projects | Scaleway


How to use the GitLab repository manager

This page shows you how to use the GitLab repository manager InstantApp on your C1 server.


  • You have an account and are logged into
  • You have configured your SSH Key

GitLab is a web-based Git repository manager with wiki and issue tracking features. GitLab includes git repository management, code reviews, an issue tracking, wiki’s and much more.

There are three steps to deploy the GitLab InstantApp

  • Create and start a new C1 server
  • Open the mail ports to send e-mail
  • Log into GitLab

Step 1 - Create the GitLab server

Before starting, click the “Create Server” button in the control panel.

You will land on the server-creation page where you must input basic information for your server.

After inputting your server basic information, you have to select the GitLab application image for your server. On the ImageHub tab, select GitLab. The server will be created with a ready to use GitLab.

Click the “Create Server” button, this action creates and starts your server.

Step 2 - Open the mail ports to send e-mail

To avoid spam, remote mail ports cannot be reached from our infrastructure by default. As GitLab requires to send mail, we need to open them.

On the left panel of the Control Panel, click on “Security”, you will land on the security-groups page. Click the “Create Group” button and input the security group name and description.

Then, on the GitLab security group, set “Block SMTP” to No.

Back to the server view, click the “Show” button to display advanced options and select the security group you previously create. Restart your server to apply the change.

Step 3 - Log into GitLab

Your GitLab C1 server is now configured and ready to use. When your server is running, copy its public IP address and paste it in your favorite browser.

Log into GitLab with the default login root and password 5iveL!fe.

Change the password for the root user.

Configure GitLab from the “Admin area”.

You now have a GitLab server configured and ready to use.

This is a companion discussion topic for the original entry at