The table below lists Git configuration properties.
|Version number of this configuration file.
|Boolean value that determines whether to use secure socket layer for HTTP communication.
|Absolute path on the server to the server key file; MUST when HTTPS protocol is to be used.
|Absolute path on the server to the certificate file; MUST when HTTPS protocol is to be used.
|Boolean value that determines if a HTTP listener has to be set up; this listener diverts the incoming requests to the same endpoint over HTTPS.
|Integer value that defines the port on which the server has to listen to.
|Timeout (in milliseconds) to be set for socket connection. Default is 3 minutes. Set to 0 for indefinite.
|Absolute path to the Git executable on the server; mention the absolute path, if git is not found on the PATH environment variable.
|Absolute path to the directory on the server where the Git repositories are located.
|Set of authentication profiles available. It is a map - the profile name is the key and the properties are the value. The value object must contain type property as one of LDAP, BASIC (case-sensitive). In case of LDAP authentication, the value object should have properties pertaining to LDAP authentication. Some basic properties are listed here. However, you can add others if required. The list of properties is documented here: https://github.com/vesse/node-ldapauth-fork#ldapauth-config-options. In case of BASIC authentication, the value object should have url and method properties against which the HTTP Basic authentication is done. If method property is absent, GET is used.
|Set of URL prefix to be considered as Git request. It is a map and the prefix is the key. The properties are the value. The value object may contain authProfile property as one of the profile names in Auth-Profiles configuration property. If authProfile property is defined, the corresponding auth profile is applied; otherwise, no authentication is performed.