Open WadeBarnes opened 1 year ago
Basic instructions for running IndyScan using docker compose:
Example docker compose configuration and settings for the Sovrin networks:
Based on this I figure we could have something running on OpenShift within a few hours. Developing and testing the configurations for CANdy and BCovrin using docker compose could be done in under and hour.
Although a single instance could be configured to scan both CANdy and BCovrin networks it's best to keep them separate.
Given that we have now reset BCovrin, this is lowered in priority -- for now :-). The current interface is fine given the size of the ledger. Nice to have IndyScan added at some point, but not crucial.
@WadeBarnes I believe this is done - maybe just partially?
Partially, just for BCovrin Test; http://test.bcovrin.vonx.io:3707/home/BCOVRIN_TEST
Do we need to run one for CANdy, or is the IDLab one sufficient?
Do we need to run one for CANdy, or is the IDLab one sufficient?
They had talked about retiring their instance due to availability concerns with their ISP that was out of their control. That was a while back. Not sure if it's still a concern. That's the only reason the CANdy environments are on the list.
Deploy an instance of IndyScan into OpenShift or AWS configured to scan the CANdy and BCovrin ledgers.
Required Work:
Acceptance Criteria:
dev
,test
, andprod
ledgersdev
test
prod
dev-greenlight
,greenlight
,dev
,test
, andprod
ledgers.dev-greenlight
greenlight
dev
test
- http://test.bcovrin.vonx.io:3707/home/BCOVRIN_TESTprod