Linux OS supports working with the Git version control system. To connect to Git, install the libgit2 package of 0.28.* version.
Connection settings are specified for each repository in the Metabases.xml file or in the registry and are further exported to the registry.reg file:
VcsLocalPath and VcsStoredPath. The path to the folder with the cloned repository that stores local object files.
VcsName. Version control system type - Git.
NOTE. To work with the Git version control system, it is supposed that the repository is already created and is cloned locally.
If authorization is required to connect to the remote repository, one can use only SSH for this purpose. To do this, in the registry key [HKEY_CURRENT_USER\Software\Foresight\Foresight Analytics Platform\10.0\DevEnv\Git] add the following keys:
UserName. Name of the user who is used for authorization.
SshkeyPath. The path to privacy SSH key. The folder with the privacy key should also contain a public key (name: <privacy key name>.pub).
The obtained registry key should be exported to a file and saved to the Linux home directory with the registry.reg file.
The user name in the registry may be omitted but in this case the path to the remote repository specified in the /.git/config file should look as follows: ssh://<user name>@<host.subdomain.domain>:<port>/<path to remote repository>
The guide for generating SSH keys for Azure Devops is available at https://docs.microsoft.com/en-us/azure/devops/repos/git/use-ssh-keys-to-authenticate?view=azure-devops.
See also: