Closed tdiesler closed 2 years ago
Currently we start the VON-Network like this ...
./manage up --logs
Then, the Aca-Py cloud agent like this ...
docker run -it --rm \ --name acapy \ -p ${ACAPY_USER_PORT}:${ACAPY_USER_PORT} \ -p ${ACAPY_ADMIN_PORT}:${ACAPY_ADMIN_PORT} \ nessus/aries-cloudagent start \ --genesis-url http://host.docker.internal:9000/genesis \ --endpoint http://${ACAPY_HOST}:${ACAPY_USER_PORT} \ --inbound-transport http 0.0.0.0 ${ACAPY_USER_PORT} \ --outbound-transport http \ --storage-type indy \ --admin 0.0.0.0 ${ACAPY_ADMIN_PORT} \ --admin-api-key adminkey \ --jwt-secret jwtsecret \ --multitenant \ --multitenant-admin \ --seed 000000000000000000000000Trustee1 \ --wallet-storage-type default \ --wallet-key trusteewkey \ --wallet-name trustee \ --wallet-type indy \ --recreate-wallet \ --auto-provision \ --auto-ping-connection \ --auto-accept-requests \ --log-level info
and the Tails Server, which is needed for revocation support, not at all.
This should be done by a common docker compose script
Depends On: https://github.com/hyperledger/aries-cloudagent-python/issues/1745
Done
Currently we start the VON-Network like this ...
Then, the Aca-Py cloud agent like this ...
and the Tails Server, which is needed for revocation support, not at all.
This should be done by a common docker compose script