GitLab Self-managed
This article contains information on how to add Gitlab Self-managed organization to GitProtect.
Adding Gitlab Self-managed organization to GitProtect
To add a Gitlab Self-managed organization to GitProtect go to the DevOps tab on the left side of the window, expand it and select Gitlab.
Now hit the GitLab Self-Managed button
Due to the fact, that you selected Gitlab Self-managed from DevOps drop-down list, the appropriate Git environment has been selected. You don't need to select Gitlab Self-managed in the Authentication section.
In the Settings tab, you need to register the GitProtect app. GitProtect will ask about the Service address (for example http://192.168.1.150 - the protocol is required!) of your Gitlab environment and will require you to select a Personal Access Token from the Password Manager (if exist) or add a new one.
See also how to add a new Personal Acces Token to the Safe Password Manager:
pageAdd A New PasswordYou can also decide whether GitProtect should have access to GitLab groups and can back up them - thanks to the Protect group switch.
The last thing, which is available to configure is the switch responsible to automatically add a new repositories to the GitProtect panel, if its will appeared in GitLab.
The last section to configure is the Repositories list sync options.
In general, during the adding process, you can specify the hours, when GitProtect should synchronize with your GitLab, or set a time interval.
Before hitting the Proceed button, pay attention to the default device.
The default device is the device assigned to GitProtect that is used to retrieve GitLab organization and their data. It also performs the backup plan itself.
By default, application uses device marked with main icon, but you can choose, which device should be responsible for performing this operation by clicking the Change button and selecting one of the devices from the list.
Now the adding process is finished. You can hit the Proceed button.
Last updated
