You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the VCX CI, we build and release the indyvdr-proxy docker image, as the indyvdr repo does not do this.
We also have a client component in VCX, which allows indy ledger interactions (anoncreds/DIDs read/write) to be performed via the client pointing to a running instance of the image.
This was previously developed by folks at Absa, however it hasn't been used in awhile and can be a burden to maintain (indy is generally full of legacy code).
This is opening a discussion about whether we still need these components within the VCX codebase.
The text was updated successfully, but these errors were encountered:
As part of the VCX CI, we build and release the indyvdr-proxy docker image, as the indyvdr repo does not do this.
We also have a client component in VCX, which allows indy ledger interactions (anoncreds/DIDs read/write) to be performed via the client pointing to a running instance of the image.
This was previously developed by folks at Absa, however it hasn't been used in awhile and can be a burden to maintain (indy is generally full of legacy code).
This is opening a discussion about whether we still need these components within the VCX codebase.
The text was updated successfully, but these errors were encountered: