- Installation Requirements.
- If you want to access your GitLab instance via a domain name, like
mygitlabinstance.com, make sure the domain correctly points to the IP of the server where GitLab is being installed. You can check this using the command
- If you want to use HTTPS on your GitLab instance, make sure you have the SSL certificates for the domain ready. (Note that certain components like Container Registry which can have their own subdomains requires certificates for those subdomains also.)
- If you want to send notification emails, install and configure a mail server (MTA) like sendmail. Alternatively, you can use other third party SMTP servers.
These configuration settings are commonly used when configuring Omnibus GitLab. For a complete list of settings, see the README file.
- Installing GitLab.
- Setting up a domain name/URL for the GitLab Instance so that it can be accessed easily.
- Enabling HTTPS.
- Enabling notification emails.
- Enabling replying via email.
Enabling container registry on GitLab.
- You will require SSL certificates for the domain used for container registry.
Enabling GitLab Pages.
- If you want HTTPS enabled, you will have to get wildcard certificates.
- Enabling Elasticsearch.
- GitLab Mattermost Set up the Mattermost messaging app that ships with Omnibus GitLab package.
- GitLab Prometheus Set up the Prometheus monitoring included in the Omnibus GitLab package.
- GitLab High Availability Roles.
You can also use the Docker images provided by GitLab to install and configure a GitLab instance. Check the documentation to know more.