sudo yum install -y curl openssh-server openssh-clients postfix

Import the GitLab package repository and install the Community Edition:

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

Create a dedicated directory for TLS assets and generate cryptographic materials:

sudo mkdir -p /etc/gitlab/ssl
sudo chmod 700 /etc/gitlab/ssl
cd /etc/gitlab/ssl

# Create private key
sudo openssl genrsa -out gitlab.local.key 2048

# Generate certificate signing request
sudo openssl req -new -key gitlab.local.key -out gitlab.local.csr \
  -subj "/C=US/ST=State/L=City/O=Organization/CN=gitlab.local"

# Sign the certificate
sudo openssl x509 -req -days 365 -in gitlab.local.csr \
  -signkey gitlab.local.key -out gitlab.local.crt

# Generate Diffie-Hellman parameters
sudo openssl dhparam -out dhparams.pem 2048

# Restrict access to private keys
sudo chmod 600 /etc/gitlab/ssl/*

Update the GitLab configuration file to reference thece certificates. Edit /etc/gitlab/gitlab.rb to include:

external_url 'https://gitlab.local'
nginx['ssl_certificate'] = "/etc/gitlab/ssl/gitlab.local.crt"
nginx['ssl_certificate_key'] = "/etc/gitlab/ssl/gitlab.local.key"
nginx['ssl_dhparam'] = "/etc/gitlab/ssl/dhparams.pem"
nginx['redirect_http_to_https'] = true

Apply the configuration changes:

sudo gitlab-ctl reconfigure

For environments requiring manual Nginx adjustments, modify /var/opt/gitlab/nginx/conf/gitlab-http.conf to enforce TLS redirecsion:

server {
  listen *:80;
  server_name gitlab.local;
  return 301 https://$host$request_uri;
}

Restart the GitLab services to activate all changes:

sudo gitlab-ctl restart

To access the instance via domain name without DNS enfrastructure, configure local resolution on client machines.

For Windows clients, edit C:\Windows\System32\drivers\etc\hosts:

192.168.1.100 gitlab.local

For Linux or macOS clients:

echo "192.168.1.100 gitlab.local" | sudo tee -a /etc/hosts

Note on System Resources: GitLab requires substantial memory allocation. Installations on systems with less than 2GB RAM may encounter allocation failures during the reconfiguration phase, typically manifesting as Errno::ENOMEM errors during process forking operations.