Getting started with Managed Service for GitLab

To get started with the service:

1. Create an instance.
2. Set up a working environment.
3. Add SSH keys to GitLab.
4. Start using the repository.

For more information about the differences between Managed Service for GitLab and the GitLab Community Edition custom installation, see the Service advantages over a GitLab custom installation section.

Getting startedGetting started

Create an instanceCreate an instance

Set up a working environmentSet up a working environment

1. Activate the Managed Service for GitLab instance:

   1. Follow the link you received in your administrator mailbox after creating the instance.
   2. Change the administrator password.
   3. Log in using the administrator username and password.

2. (Optional) Create a group to host the repository project.

   If there are several projects, you might want to group users together. This will allow you to:

   • Grant rights for specific projects to each group.
   • View issues and merge requests by group.
   • View analytics on group's activities.

   For more information, see the relevant GitLab documentation.

3. Create an empty project to host the repository.

4. Create users and add them to a group or project with the Maintainer or Owner role.

   You can only add your team members to a group or project by creating GitLab accounts for them.

Add SSH keys to GitLabAdd SSH keys to GitLab

1. Create a pair of public and private SSH keys for the GitLab account:

   Linux/macOS

   Windows 10/11

   Windows 7/8

   1. Open the terminal.

   2. Use the ssh-keygen command to create a new key:

      ssh-keygen -t ed25519 -C "<optional_comment>"
      

      You can specify an empty string in the -C parameter to avoid adding a comment, or you may not specify the -C parameter at all: in this case, a default comment will be added.

      After running this command, you will be prompted to specify the name and path to the key files, as well as enter the password for the private key. If you only specify the name, the key pair will be created in the current directory. The public key will be saved in a file with the .pub extension, while the private key, in a file without extension.

      By default, the command prompts you to save the key under the id_ed25519 name in the following directory: /home/<username>/.ssh. If there is already an SSH key named id_ed25519 in this directory, you may accidentally overwrite it and lose access to the resources it is used in. Therefore, you may want to use unique names for all SSH keys.

   If you do not have OpenSSH installed yet, follow this guide to install it.

   1. Run cmd.exe or powershell.exe (make sure to update PowerShell before doing so).

   2. Use the ssh-keygen command to create a new key:

      ssh-keygen -t ed25519 -C "<optional_comment>"
      

      You can specify an empty string in the -C parameter to avoid adding a comment, or you may not specify the -C parameter at all: in this case, a default comment will be added.

      After running this command, you will be prompted to specify the name and path to the key files, as well as enter the password for the private key. If you only specify the name, the key pair will be created in the current directory. The public key will be saved in a file with the .pub extension, while the private key, in a file without extension.

      By default, the command prompts you to save the key under the id_ed25519 name in the following folder: C:\Users\<username>/.ssh. If there is already an SSH key named id_ed25519 in this directory, you may accidentally overwrite it and lose access to the resources it is used in. Therefore, you may want to use unique names for all SSH keys.

   Create keys using the PuTTY app:

   1. Download and install PuTTY.

   2. Add the folder with PuTTY to the PATH variable:

      1. Click Start and type Change system environment variables in the Windows search bar.
      2. Click Environment Variables... at the bottom right.
      3. In the window that opens, find the PATH parameter and click Edit.
      4. Add your folder path to the list.
      5. Click OK.

   3. Launch the PuTTYgen app.

   4. Select EdDSA as the pair type to generate. Click Generate and move the cursor in the field above it until key creation is complete.

      

   5. In Key passphrase, enter a strong password. Enter it again in the field below.

   6. Click Save private key and save the private key. Do not share its key phrase with anyone.

   7. Click Save public key and save the public key to a file named <key_name>.pub.

2. Launch the SSH agent:

   Linux/MacOS

   Windows

   1. Run this command:

      ssh-agent -s
      

   2. For the SSH agent to start on login, add the launch command to the ~/.profile file:

      ssh-agent -s
      

   1. Open the Start button context menu.
   2. Select Computer Management.
   3. Go to Services and Applications → Services.
   4. Open the context menu of the SSH agent service and select Properties.
   5. On the Main tab, change the startup type from Off to Automatic.
   6. Click OK and start the service.

3. Add a key to the SSH agent:

   ssh-add <private_key_path>
   

4. Assign a public SSH key to the GitLab account.

5. Check that you can connect to GitLab:

   ssh -T git@<GitLab_instance_domain>
   

   Example:

   ssh -T git@example.gitlab.yandexcloud.net
   

   If connecting for the first time, you will get this or similar message:

   The authenticity of host 'gitlab.example.com (35.231.145.151)' can't be established.
   ECDSA key fingerprint is SHA256:HbW3g8zUjNSksFbqTiUWPWg2Bq1x8xdGUrliXFzSnUw.
   Are you sure you want to continue connecting (yes/no)? yes
   Warning: Permanently added 'gitlab.example.com' (ECDSA) to the list of known hosts.
   

   Type yes and press Enter.

   If it is not your first time, you will get this upon a successful connection:

   Welcome to GitLab, @<login>!
   

   In case of an error, run the connection in Verbose mode to get the logs:

   ssh -Tvvv git@<GitLab_instance_domain>
   

Ask each member of your group or project to create an SSH key pair this way and assign the public key to their account in GitLab.

Start using the repositoryStart using the repository

To start working with a local copy of your repository using the account you created, follow the steps below on your local computer:

1. Install the Git client.

2. Clone the repository using the SSH protocol.

   What to do if you get the Permission denied (publickey) error

   When cloning, you may get this error:

   Cloning into '<project_name>'...
   git@<GitLab_instance_domain>: Permission denied (publickey).
   fatal: Could not read from remote repository.
   
   Please make sure you have the correct access rights
   and the repository exists.
   

   If you get this error:

   1. Create and open a configuration file to set up SSH keys:

      nano ~/.ssh/config
      

   2. Add content to it:

      Host <GitLab_instance_domain>
         IdentityFile <private_key_path>
      

      In the IdentityFile parameter, specify the absolute path to the private key you created for the GitLab project.

   3. Save the file.

   4. Clone the repository again via SSH.

3. Go to the repository folder:

   cd <project_name>
   

4. Make changes to the repository files.

5. Index and apply the changes in the local repository:

   git add . && git commit -m "<commit_name>"
   

6. Push the changes to the remote repository:

   git push origin main