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


#1

How to use the GitLab repository manager

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

Requirements

  • You have an account and are logged into cloud.scaleway.com
  • 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.

Try this tutorial on your own C1 server TRY IT


This is a companion discussion topic for the original entry at https://www.scaleway.com/docs/how-to-use-the-gitlab-instant-apps/

#2

How can i set up a subdomain i own on another provider, git.mydomain.com to point to this? I’ve set the A record for the sub-domain but it does not work.


#3

If I remember, gitlab use nginx. You can modify the name in the vhost. That allow to see the web interface.

To clone, push or pull, your have to modify the name (git.mydomain.com) in the config of gitlab itself. It’s depending how the install is build. Look for a “config.rb” file or “config” directory with e path containing “gitlab”. Mine is in /home/gitlab because of the tutorial I follow a year ago.


#4

@Mazarini I tried that. But i can’t find the setting file for NGINX in the one click installed version of this Gitlab. I’ve edited the config.rb file to reflect my domain name, but then Gitlab stopped working, shows a 502 error, that it’s taking too long. I changed it back to the original but it still won’t run. I have to delete the instance and start all over again.


#5

For nginx vhost use by Debian : /etc/ngnix/site-available/* (don’t know if you use Debian, but other can be similar).
May be, gitlab is the default site. Try using the public IP and then verify that git.domain.com correspond to your public IP with ping git.domain.com (can take 24h between dns modify and dns take it)

For config.rb, may be you miss a quote or double quote when modify. If gitlab is down, nginx don’t have response and can just answer 502. Modify this is not the fist to do. I believe you can work without for update your project by using http and not ssh.


#6

@Mazarini I looked into the /etc folder and there isn’t a “nginx” folder.

Followed the security settings to set “Block SMTP” to No, but I’m still not receiving any emails.


#7

You can unblock smtp from scaleway manager (choice sécurity). Not in “group rules” but globaly with a radio button “Block SMTP”.
When I do that, I have to reboot my server to activate the changes.

Try to know what linux you use (Debian, Centos…) and what logiciel is installed. It will be easyer to help you and to search tutorials. I just know Debian as beginner.


#8

I got the same issue.
If I look in exim log, I find

xxxxxx.pub.cloud.scaleway.com R=nonlocal: Mailing to remote domains not supported

So, I think default exim conf does not allow sending mail.


#9

Out of curiosity, is there a similarly easy way to configure the GitLab instances to work with SSL from Let’s-Encrypt (or some other source), or do we just go about running the Let’s Encrypt script for NGinX? (which doesn’t work properly as of right now without a plugin I believe).