Commands
In this article, we will review the top 10 most commonly used Git commands. You can’t call yourself a competent DevOps Engineer or IT professional
Learn how to effortlessly install GitLab CE on your RHEL 9 or CentOS 9 system with our comprehensive guide. Follow our step-by-step instructions for a smooth setup and unlock the full potential of GitLab’s powerful features for your development projects.
Are you eager to set up GitLab CE on your RHEL 9 or CentOS 9 system? Great choice! GitLab is a robust platform for managing your Git repositories, CI/CD pipelines, and much more—all in one place. In this guide, we’ll walk you through the installation process step by step, ensuring a smooth setup on your Red Hat Enterprise Linux or CentOS environment.
Before diving into the installation, let’s ensure we have all the necessary prerequisites:
We’ve configured our RHEL 9 instance with the following settings:
| Hostname | gitlab.naijalabs.net |
| IP address | 192.168.1.24 |
| RAM | 8 GB |
| Cores | 2 |
First things first, let’s ensure our system packages are up to date. Open your terminal and execute the following command:
sudo dnf update
This command will update all the packages to their latest versions, ensuring compatibility and security patches are in place.
GitLab has a few dependencies that need to be installed. Use the following command to install them:
sudo dnf install -y curl policycoreutils openssh-server openssh-clients
Now it’s time to install the GitLab CE repositories on your system. Run the following command:
curl -sS https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.rpm.sh | sudo bash
Once the repository is added, install GitLab CE using DNF:
sudo dnf install -y gitlab-ce
Photo by admingeek from Infotechys
After installation, we need to configure GitLab. Open the GitLab configuration file using your preferred text editor. Here, we’ll use Vim:
sudo vim /etc/gitlab/gitlab.rb
Within this file, you can configure various settings according to your preferences, such as external URL, SMTP settings, and more. Make necessary changes, then save and close the file.
## GitLab URL
##! URL on which GitLab will be reachable.
##! For more details on configuring external_url see:
##! https://docs.gitlab.com/omnibus/settings/configuration.html#configuring-the-external-url-for-gitlab
##!
##! Note: During installation/upgrades, the value of the environment variable
##! EXTERNAL_URL will be used to populate/replace this value.
##! On AWS EC2 instances, we also attempt to fetch the public hostname/IP
##! address from AWS. For more details, see:
##! https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instancedata-data-retrieval.html
external_url 'http://localhost:7000'
After modifying the configuration, reconfigure GitLab to apply the changes:
sudo gitlab-ctl reconfigure
Execute the following command(s) to confirm that ports 80, 443, and 7000 are accessible for inbound and outbound traffic:
sudo firewall-cmd --add-port=80/tcp --add-port=443/tcp --add-port=7000/tcp --permanent; sudo firewall-cmd --reload
Once the reconfiguration is complete, you can access GitLab via your web browser. Simply navigate to the URL you specified in the configuration file (e.g., http://localhost:7000 or server-IP-address:7000).
Photo by admingeek from Infotechys
Install Nginx with the following command:
sudo dnf -y install nginx
Create a gitlab.conf file to setup nginx as proxy:
sudo vim /etc/nginx/conf.d/gitlab.conf
Copy and paste the following content into the file. Then, save and exit the file.
server {
listen 80;
listen [::]:80;
listen 443 ssl http2;
listen [::]:443 ssl http2;
server_name gitlab.naijalabs.net;
ssl_certificate "/etc/letsencrypt/live/naijalabs.net/fullchain.pem";
ssl_certificate_key "/etc/letsencrypt/live/naijalabs.net/privkey.pem";
ssl_session_cache shared:SSL:1m;
ssl_session_timeout 10m;
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
location / {
proxy_pass http://localhost:7000;
}
}
NOTE: Ensure the paths to
ssl_certificateandssl_certificate_keypoint to where your SSL certificate and key files reside on your machine.
Run the following commands to start Nginx and enable it to autostart on boot:
sudo systemctl daemon-reload; sudo systemctl enable --now nginx
To enable network communications between Nginx and GitLab, execute the following commands to adjust the SELinux Boolean accordingly.
sudo setsebool -P httpd_can_network_connect 1; sudo setsebool -P nis_enabled 1
Well done! Your GitLab CE instance is now secure and accessible over HTTPS!
Photo by admingeek from Infotechys
Your initial login credentials are located in the /etc/gitlab/initial_root_password file for the root user. You can also reset the root password with the following command:
sudo gitlab-rake "gitlab:password:reset[root]"
Photo by admingeek from Infotechys
Related Posts
In this article, we will review the top 10 most commonly used Git commands. You can’t call yourself a competent DevOps Engineer or IT professional
In this article, we will review installing and using Git on Linux machines. Besides minor differences in syntax, the install commands and procedures are similar
In this article, we will examine installing and using Gitlab on Ubuntu server version 20.04. Gitlab community edition or Gitlab CE can be installed by