You could earn up to $300 by adding new articles!Get Started Now
This article contains information about the GitLab application that can be deployed on Vultr.
To launch a GitLab application on Vultr, a plan of at least 2GB RAM and 2 CPU cores is needed.
GitLab runs on the CentOS 6 x64 operating system. It is the GitLab Community Edition (CE) flavor. You can log into this system with an SSH client using the root login found on your Vultr control panel.
To access the GitLab application, navigate to
https://[SERVER_IP]/ in your web browser. Substitute the
[SERVER_IP] with the IP address of your VPS. It can take several minutes before this URL becomes accessible after launching the application. The SSL certificate warning can be safely ignored. This is explained in further detail below. Your GitLab login credentials are listed in the Vultr control panel.
Your GitLab server can be accessed with either
https:// URLs. Accessing with
http:// will automatically redirect you to
https://. By default, the
https:// URL uses a self-signed certificate, which displays a security warning. This can be safely ignored.
Depending on your plans for your GitLab server, you may want to update the certificate to one provided by an actual certificate authority. This will remove the security warning error and allow you to clone repositories over HTTPS with Git. To install a new certificate, do the following:
/etc/gitlab/ssl/with the updated certificate. Details on converting certificate formats are outside of the scope of this article.
If you plan on using a domain with your GitLab server, you will need to point the DNS "A record" to your
[SERVER_IP]. This will allow you to access GitLab by navigating to your website (
https://www.example.com). You must also switch the URL in the GitLab configuration. This will correct the "clone URLs" displayed within GitLab. Follow the steps below.
/etc/gitlab/gitlab.rband edit the line
Your Git repositories created and managed by GitLab are located in
Vultr applications use modern releases of software packages. Applications are configured to be deployed with specific versions of software. Over time, the Vultr team will update the application offerings to include newer operating systems, package versions, etc. This document only provides up-to-date information about the latest version of this application. Vultr applications are updated without notice. If you plan to build a project or infrastructure based on our application templates, we recommend taking a snapshot of the application used in your initial deployment.