Getting Started with GitLab
This article is designed to help you get started with your GitLab instance.
Web Interface Login Credentials
The GitLab web interface is the central location for managing your GitLab instance.
Your login credentials, as well as the URL for the GitLab web interface, were stored in the GitLab server’s password vault in the Customer Center when your GitLab instance was provisioned.
Customize the GitLab Domain
For the initial operation of your GitLab instance, the working domain is available for both managed and unmanaged servers. If you’d like to use a different domain, you can customize the GitLab domain to any domain of your choice. To customize the GitLab domain, you’ll need the desired domain as well as the corresponding DNS records that resolve to the IP address of your GitLab server.
You can find step-by-step instructions for customizing the GitLab domain for GitLab Server in the following Help Center article: Change GitLab Domain
Email Delivery
GitLab sends emails for various actions, such as when a user registers. There are several options available for email delivery through your GitLab instance.
Sending via our Send Connector:
Sending emails via a Send Connector requires an active Send Connector.
More information about Send Connectors
For step-by-step instructions on configuring a Send Connector for sending emails in GitLab, see the following Help Center article:
Configuring a Send Connector in GitLab
Sending via Your Own SMTP Server:
For step-by-step instructions on configuring your own SMTP server for sending email in GitLab, see the following Help Center article:
Configuring the SMTP server in GitLab
Registering GitLab Runners
GitLab sends jobs from pipelines to GitLab Runners for processing. To do this, the desired GitLab Runners must be registered in your GitLab instance.
For step-by-step instructions on registering GitLab Runners in your GitLab instance, see the following Help Center article:
If you’d like our support team to register the GitLab Runners in your GitLab instance for you, please feel free to contact our support team or join our live chat. We’d be happy to register the GitLab Runners in your GitLab instance for you via Remote Hands.
Enable Garbage Collection for GitLab & Runners
After successfully registering the runners, you can optionally enable garbage collection for the primary GitLab instance as well as all registered runners to prevent old pipeline artifacts from unnecessarily taking up disk space.
Enable Garbage Collection for GitLab:
https://help.creoline.com/de/en/doc/gitlab-garbage-collection-77N1dQp6JR
Enable garbage collection for runners:
https://help.creoline.com/de/en/doc/gitlab-runner-garbage-collection-Lctk5MLO44
The cron jobs described in this article can be created either directly via SSH or through our graphical cron job system in the Customer Center. We’d be happy to set them up for you as well. Just let us know.
