Wallet backend standalone

If you are working on one of the web frontends (e.g. web-wallet, issuer-portal, verifier-portal), you may want to run the wallet backend container standalone, to connect your local web frontend build with it.

Edit the configuration files in waltid-walletkit/config, according to your needs and run the container like so:

cd waltid-walletkit
docker run -p 8080:8080 -e WALTID_DATA_ROOT=/data -v $PWD:/data waltid/walletkit run

Note: Running the web frontend containers standalone, makes little sense, as they depend on an API gateway to connect to the backend APIs. This API gateway is set up by the docker-compose configuration, mentioned above.

Docker Compose

The easiest and fastest way to get the wallet backend, frontend, and issuer and verifier portals started, is by using our docker-compose configuration, located in the waltid-walletkit project, in the subfolder:


Simply start the services using:

docker-compose up

This configuration will publish the following endpoints by default:

  • Web wallet on [HOSTNAME]:8080

    • API: /api/

  • Verifier portal on [HOSTNAME]:8081

    • API: /verifier-api/

  • Issuer portal on [HOSTNAME]:8082

    • API: /issuer-api/

Note: __ [HOSTNAME] is your local computer name. If you use localhost instead, some features, particularly with regards to credential exchange, will not work correctly.

In case the HOSTNAME is not picked up automatically, you might need to set it in an env-file and refer to it by: docker-compose --env-file env-file-with-hostname up.

Visit the ./docker folder for adjusting the system config in the following files:

  • docker-compose.yaml - Docker config for launching containers, volumes & networking

  • ingress.conf - Routing config

  • config/wallet-config.json - wallet backend configuration

  • config/verifier-config.json - verifier backend configuration

  • config/issuer-config.json - issuer backend configuration

Last updated