Deploy the Client Gateway

This demonstration is based on a locally-hosted HashiCorp Key Vault. Hence, it is one of the demo services in the docker-compose file being used.

Clone the ddhub-client-gateway GIT repository and change the working directory to `/get-started`

git clone https://github.com/energywebfoundation/ddhub-client-gateway.git && cd ddhub-client-gateway/get-started

Start the `ddhub-client-gateway` stack

The method of completing this depends on which of the three key vault services is being used:

Run the docker compose up command.

Replace the AZURE_* environment variables below with actual azure access credentials for accessing the Azure Key Vault obtained from Azure Key Vault access credentials.

Then run the command:

AZURE_VAULT_URL=key_vault_url AZURE_CLIENT_ID=client_id AZURE_CLIENT_SECRET=client_secret AZURE_TENANT_ID=tenant_id SECRETS_ENGINE=azure docker compose up

Run the docker compose up command.

Replace the AWS_* environment variables below with actual azure access credentials for accessing the Azure Key Vault obtained from AWS Secrets manager access credentials.

Then run the command:

AWS_REGION=aws_region AWS_ACCESS_KEY_ID=aws_access_key_id AWS_SECRET_ACCESS_KEY=aws_secret_access_key SECRETS_ENGINE=aws docker compose up

The docker compose file for Hashicorp Vault secret engine (1) initializes the vault, (2) auto-unseals it, and (3) passes the vault_token to the DDHub service.

Optionally, more details on what can be done manually are available here: Scenario-2: Deploy new HashiCorp vault service and obtain token - run a single container

docker compose -f ./docker-compose.vault.yml up

PreviousDeploy with Docker NextVisit the Client Gateway

Last updated 2 months ago

Clone the ddhub-client-gateway GIT repository and change the working directory to /get-started

Start the ddhub-client-gateway stack

Clone the ddhub-client-gateway GIT repository and change the working directory to `/get-started`

Start the `ddhub-client-gateway` stack