How To Install GitLab on AlmaLinux 10

GitLab has become the cornerstone of modern DevOps workflows, offering developers and system administrators a comprehensive platform for version control, continuous integration, and collaborative software development. AlmaLinux 10, as the latest enterprise-grade Linux distribution, provides an excellent foundation for hosting GitLab instances with enhanced security, stability, and performance characteristics.

This comprehensive guide will walk you through the complete process of installing GitLab Community Edition on AlmaLinux 10, from initial system preparation to advanced configuration options. Whether you’re setting up a development environment or preparing a production deployment, this tutorial covers everything you need to establish a robust GitLab instance on your AlmaLinux server.

Prerequisites and System Requirements

Before beginning the GitLab installation process, ensuring your system meets the minimum requirements is crucial for optimal performance and stability.

Hardware Requirements

GitLab requires substantial system resources to operate efficiently. The minimum hardware specifications include 4 GB of RAM, 4 CPU cores, and at least 10 GB of available disk space. However, production environments should consider the recommended specifications of 8 GB or more RAM, 8+ CPU cores, and 16 GB of disk space to handle multiple users and repositories effectively.

Storage considerations extend beyond the initial installation footprint. GitLab stores repository data, artifacts, and backup files, so planning for future growth is essential. Consider implementing a separate partition or dedicated storage volume for GitLab data directories.

Software Requirements

Your AlmaLinux 10 system should have a fresh installation with root or sudo access privileges. SSH access is recommended for remote administration, particularly in production environments. Additionally, having a valid domain name configured is optional but highly recommended for professional deployments.

Network and Security Considerations

Ensure your server maintains a stable internet connection throughout the installation process. Plan your network configuration, including domain name resolution and IP address assignments. Consider SSL certificate requirements early in the planning phase, especially for production environments where HTTPS encryption is mandatory.

Pre-Installation System Preparation

Proper system preparation forms the foundation of a successful GitLab installation. This phase involves updating system packages, installing dependencies, and configuring essential services.

System Updates and Security

Begin by updating your AlmaLinux 10 system to the latest packages and security patches. Execute the following commands to ensure your system runs the most current software versions:

sudo dnf clean all
sudo dnf update -y
sudo dnf upgrade -y

These commands refresh the package cache, update existing packages, and upgrade the system to the latest available versions. The update process may take several minutes depending on your internet connection and the number of packages requiring updates.

Installing Essential Dependencies

GitLab requires specific system packages to function correctly. Install the necessary dependencies using the dnf package manager:

sudo dnf install -y curl policycoreutils openssh-server openssh-clients ca-certificates postfix

This command installs curl for downloading files, policycoreutils for SELinux management, OpenSSH components for secure remote access, CA certificates for SSL verification, and Postfix for email functionality.

Some systems may require additional packages depending on your specific configuration. If you encounter dependency conflicts, resolve them by installing packages individually and addressing any conflicts that arise.

Firewall Configuration

Configure your system firewall to allow necessary traffic for GitLab operation. AlmaLinux 10 typically uses firewalld for firewall management. Open the required ports using these commands:

sudo firewall-cmd --permanent --add-service=http
sudo firewall-cmd --permanent --add-service=https
sudo firewall-cmd --permanent --add-service=ssh
sudo firewall-cmd --reload

These commands permanently open HTTP (port 80), HTTPS (port 443), and SSH (port 22) services, then reload the firewall configuration to apply changes. Verify the firewall rules are active by running sudo firewall-cmd --list-all.

GitLab Repository Setup and Installation

The GitLab installation process involves adding the official repository and installing the GitLab Community Edition package through your system’s package manager.

Adding GitLab Official Repository

GitLab provides an automated script to add their official repository to your AlmaLinux system. This ensures you receive the latest stable version and future updates directly from GitLab’s servers.

First, download and install the GitLab GPG key for package verification:

curl https://packages.gitlab.com/gitlab/gitlab-ce/gpgkey | sudo tee /etc/pki/rpm-gpg/RPM-GPG-KEY-gitlab

Next, run the repository installation script:

curl -s https://packages.gitlab.com/install/repositories/gitlab/gitlab-ce/script.rpm.sh | sudo bash

This script automatically detects your AlmaLinux version and configures the appropriate repository settings. The script installs yum-utils if not already present and generates the necessary repository cache files.

GitLab Installation Methods

You can install GitLab using two primary methods: through the package manager or manual RPM installation.

Method A: Package Manager Installation

The most straightforward approach uses the dnf package manager with the newly configured repository:

sudo EXTERNAL_URL="http://gitlab.yourdomain.com" dnf install -y gitlab-ce

Replace “gitlab.yourdomain.com” with your actual domain name or IP address. This method automatically handles dependencies and configures basic settings during installation.

Method B: Manual RPM Installation

For environments requiring specific version control or offline installations, download the GitLab RPM package directly:

wget https://packages.gitlab.com/gitlab/gitlab-ce/packages/el/8/gitlab-ce-<version>.rpm/download.rpm
sudo dnf localinstall gitlab-ce-<version>.rpm

Replace <version> with your desired GitLab version number. This method provides greater control over the installation process but requires manual dependency management.

Installation Verification and Initial Setup

After installation completes, initialize GitLab by running the reconfiguration command:

sudo gitlab-ctl reconfigure

This process configures all GitLab components, creates necessary directories, and initializes the database. The reconfiguration process typically takes 5-10 minutes to complete and produces detailed output showing each configuration step.

Monitor the reconfiguration output for any error messages or warnings. Successful completion displays “gitlab Reconfigured!” at the end of the process.

Service Management

Verify GitLab services are running correctly:

sudo gitlab-ctl status

This command displays the status of all GitLab components, including Puma, Sidekiq, PostgreSQL, and Redis. All services should show “run” status for proper operation.

To manage GitLab services manually, use these commands:

• Start services: sudo gitlab-ctl start
• Stop services: sudo gitlab-ctl stop
• Restart services: sudo gitlab-ctl restart

GitLab Configuration and Customization

Customizing GitLab configuration ensures optimal performance and security for your specific environment and requirements.

Basic Configuration Setup

GitLab’s primary configuration file is located at /etc/gitlab/gitlab.rb. Edit this file to customize your installation:

sudo nano /etc/gitlab/gitlab.rb

The most important setting is the external URL, which defines how users access your GitLab instance:

external_url 'http://gitlab.yourdomain.com'

For production environments, use HTTPS instead of HTTP. After making configuration changes, apply them by running:

sudo gitlab-ctl reconfigure

SSL/HTTPS Configuration

Securing your GitLab instance with SSL encryption is essential for production deployments. Obtain SSL certificates through Let’s Encrypt or a commercial certificate authority.

For Let’s Encrypt certificates, modify your configuration:

external_url 'https://gitlab.yourdomain.com'
letsencrypt['enable'] = true
letsencrypt['contact_emails'] = ['admin@yourdomain.com']

GitLab can automatically obtain and renew Let’s Encrypt certificates when properly configured. For custom certificates, specify their locations:

nginx['ssl_certificate'] = "/etc/ssl/certs/gitlab.crt"
nginx['ssl_certificate_key'] = "/etc/ssl/private/gitlab.key"

Email and SMTP Configuration

Configure email settings to enable GitLab notifications and password reset functionality:

gitlab_rails['smtp_enable'] = true
gitlab_rails['smtp_address'] = "smtp.yourdomain.com"
gitlab_rails['smtp_port'] = 587
gitlab_rails['smtp_user_name'] = "gitlab@yourdomain.com"
gitlab_rails['smtp_password'] = "your-smtp-password"
gitlab_rails['smtp_domain'] = "yourdomain.com"
gitlab_rails['smtp_authentication'] = "login"
gitlab_rails['smtp_enable_starttls_auto'] = true

Test email configuration using GitLab’s built-in testing tools after reconfiguration.

Initial Access and Post-Installation Tasks

Accessing your GitLab instance for the first time requires specific steps to ensure security and proper initialization.

First-Time Access

Navigate to your GitLab URL using a web browser. The initial root password is automatically generated and stored in /etc/gitlab/initial_root_password. Retrieve this password:

sudo cat /etc/gitlab/initial_root_password

Log in using the username “root” and the password from this file. GitLab requires you to change this password immediately upon first login for security purposes.

Administrative Setup

Create additional administrator accounts and configure user management settings through the GitLab web interface. Navigate to the Admin Area to:

• Add new users and assign administrative privileges
• Configure authentication settings
• Set up user groups and project permissions
• Configure runner registration for CI/CD pipelines
• Establish backup procedures and schedules

Security Hardening

Implement additional security measures beyond the default configuration:

• Enable two-factor authentication for all administrative accounts
• Configure IP address restrictions for sensitive areas
• Set up audit logging for compliance requirements
• Implement regular security scanning and vulnerability assessments
• Configure automated backup procedures with offsite storage

Review GitLab’s security configuration guidelines regularly to maintain optimal protection against emerging threats.

Maintenance and Troubleshooting

Regular maintenance ensures your GitLab instance continues operating efficiently and securely over time.

Regular Maintenance Tasks

Update GitLab regularly to receive security patches and new features:

sudo dnf update gitlab-ce
sudo gitlab-ctl reconfigure

Implement automated backup procedures using GitLab’s built-in backup tools:

sudo gitlab-backup create

Schedule regular backups using cron jobs and store backup files in secure, offsite locations. Monitor system resources and log files to identify potential issues before they impact users.

Common Issues and Solutions

Installation failures often result from insufficient system resources or dependency conflicts. Verify your system meets minimum requirements and resolve any package conflicts before retrying installation.

Service startup problems may indicate configuration errors or resource constraints. Check GitLab logs using:

sudo gitlab-ctl tail

Memory and performance issues typically require increasing system resources or optimizing GitLab configuration settings. Monitor resource usage and adjust settings accordingly.

Permission problems often stem from SELinux policies or file system permissions. Verify SELinux contexts and file ownership match GitLab requirements.

Advanced Management Commands

GitLab provides numerous management commands for advanced administration:

• Check configuration: sudo gitlab-ctl diff-config
• View service logs: sudo gitlab-ctl tail <service-name>
• Restart specific services: sudo gitlab-ctl restart <service-name>
• Perform database migrations: sudo gitlab-rake db:migrate
• Clear cache: sudo gitlab-rake cache:clear

These commands enable precise control over GitLab operations and troubleshooting specific issues.

Uninstallation Process

If you need to remove GitLab from your system, follow these steps to ensure complete removal:

Stop all GitLab services:

sudo gitlab-ctl stop

Remove the GitLab package:

sudo dnf remove gitlab-ce

Clean up remaining configuration and data files:

sudo rm -rf /etc/gitlab /var/opt/gitlab /var/log/gitlab

Warning: This process permanently deletes all GitLab data, including repositories, issues, and user accounts. Ensure you have complete backups before proceeding with uninstallation.

Congratulations! You have successfully installed GitLab. Thanks for using this tutorial for installing GitLab on your AlmaLinux OS 10 system. For additional help or useful information, we recommend you check the official GitLab website.