Service Configuration

By default, ThrillConnect will create default configurations for its dependencies and you will usually need to change these.

NOTE You will need to have an authenticated Bearer token in order to use the APIs described in this section

Authenticating

Authenticate using an administrative account via Thrill-ID. You can refer to the Thrill-ID documentation for more information, but below is an example:

  • Request: POST https://thrill-id.hostname/accounts/auth
  • Body (JSON):
{
    "username": "admin@thrilltech.io",
    "password": "password"
}

Once you have your token, you can proceed with updating the service configuration.

Updating Service Configuration

There are currently 2 service dependencies that can be configured for ThrillConnect:

  • ThrillPots
  • BitBridge

Updating the configuration for either of these services follows the same process as outlined below.

Example: Updating ThrillPots service host

In this example, we will update the host for the ThrillPots service which allows ThrillConnect to successfully communicate with ThrillPots. Let us imagine that we wish to change the host to host.docker.internal:8084, we would send the following message to ThrillConnect:

  • Request: POST https://thrillconnect.host-name/v1/admin/service
  • Headers:
    • Authorization: Bearer [TOKEN]
  • Body (JSON):
{
    "id": "thrillpots",
    "host": "http://host.docker.internal:8084",
}