feat: allow git-proxy to be configured both by environment as well as config file(s)

Tracking overall enhancements to how the git-proxy application receives its user configurable values. 


```[tasklist]
### Tasks
- [ ] Allow all user settings to be defined in a JSON file (largely complete but remove any hard-coded values from src)
- [ ] Allow `GIT_PROXY_*` environment variables to override file-based settings
- [ ] Add test cases to configuration parsing for all settings (improve coverage)
- [ ] Adopt a [proper library to handle externalized config](https://www.npmjs.com/package/config)
```

 ---

> LGTM - as a future enhancement, we should expose the server ports as both file-based config (via [proxy.config.json](https://github.com/finos/git-proxy/blob/main/proxy.config.json)) as well as environment variables. We should have this available for all our configurable values, merge or reconcile between the two sources and allow users to choose whichever method best suits their deployment to configure ports & other values.

_Originally posted by @coopernetes in https://github.com/finos/git-proxy/pull/379#pullrequestreview-1802800723_
            

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: allow git-proxy to be configured both by environment as well as config file(s) #382

Tasks

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development