You can configure various options using environemnt variables. See https://github.com/Azure/git-rest-api/blob/master/src/config/schema.ts
**Note: There is no authentication layer yet from your service to the docker image. You should most likely use in in a contained environment(Inside a VNet or kubernetes cluster for example)**
# Use the API
* Using the Javascript sdk
A javascript sdk is always included and up to date with the latest version of the service.
```
npm install --save git-rest-api-sdk
```
* Use rest api
There is a `/swagger` endpoint which serve the swagger UI with all the api you can use and help you figure out the available/required params.
To authenticate against the repo if its not public you have 2 options:
-`x-authorization`: This needs to be in a Basic auth format(`Basic base64(usename:password)`). Check with the git server how you can authenticate.
-`x-github-token`: This is an helper for authnetication against github api. The basic header will be generated automatically
- Long path issue. libgit2(library behind nodegit) doesn't support windows long path feature. Which means some repo with long reference might not work on windows. You can test with other simpler repos on windows. You should however not use this in production on windows.