Configuration parameters are set via environment variables or JSON configuration (the path to it is passed as a parameter when starting the server).

After the first launch, the parameters are cached in CodeHistory.profile.db. The cache is updated every time the service is started with new parameters.

The configuration can be initialized or changed in the server web interface

Repo config screen:

Issue tracker config screen:

It is only available to users with the ADMIN role.

Here's an example of config.json content for a PDFBox repository:

{
  "REPO_PATH": "pdfbox",
  "REPO_URL": "https://github.com/apache/pdfbox",
  "REPO_FOLLOW_URL": "https://github.com/apache/pdfbox"
  "REPO_TYPE": "GITHUB",
  "REPO_COMMIT_URL_TEMPLATE": "%s/commit/%s",
  "ISSUE_TRACKER_TYPE": "JIRA",
  "ISSUE_TRACKER_URL": "https://issues.apache.org/jira",
  "DEFAULT_BRANCH": 'refs/remotes/origin/master',
}


In case of JSON config file passed as a parameter argument:

java -jar codehistory.jar config.json

Environment variables have a higher priority than JSON config (override them).