Deployment

The VCMS test deployments and related docker compose files showcase and extended deployment environment, includes containers like web applications that are usually not needed in each environment. This page describes which containers are suggested for which use-case.

Further notes about the components is available at Component View

Additional containers not described on this page are not suggested for deployment.

Mandatory containers

The following containers are mandatory for each VCMS deployment:

Container name	Description
svc-aca-py	The ACA-Py agent implementation
svc-aries-facade	This is the only service that directly calls ACA-Py
svc-webhook	Receives events coming from ACA-Py, and places them on RabbitMQ for further access. Takes care of managing the RabbitMQ configuration
svc-rabbitmq	Message queuing for events originating from AcaPy to be used by the VCMS services.
svc-tails-server	Manages the Revocation Tails files. It is a mandatory deployment even if the revocation function is not used.

Besides these containers a running Postgres database is also necessary. This resource is currently manually managed for VCMS.

Additional containers per feature

Based on the use-case and need these container might be deployed:

Container name	Description
api-issuer	Providing the public endpoint for VC issuing and revoking
api-verifier	Providing the public endpoint for VC proof presenting and verification
api-connector	Providing the public endpoint for creating and managing DIDCOMM invitations