Reg-pilot related information, issues, discussions, and more.
- signify-ts-test: integration scripts and tests to simulate use cases for the whole reg-pilot.
- proxy-server: simulates a scenario when a proxy service sits between the client and reg-pilot-api.
- reg-webapp github and reg-webapp docker development images
- reg-pilot-api github and development reg-pilot-api docker development images
- vlei-verifier github and development vlei-verifier docker development images
- You might find these visual instructions useful from a Oct 2024 demo walkthrough
- Demo keria instance url =
https://keria-dev.rootsid.cloud/admin
and boot url =https://keria-dev.rootsid.cloud
- Demo signify passcode =
Ap31Xt-FGcNXpkxmBYMQn
- Demo reg-webapp: Test | Dev currently requires the signify-browser-extension to be installed
- Demo reg-pilot-api: Test - ping it | Dev - ping it
- Demo witness urls:
"https://witness-dev01.rootsid.cloud", "https://witness-dev02.rootsid.cloud", "https://witness-dev03.rootsid.cloud"
- Demo vlei schema server:
"http://schemas.rootsid.cloud"
At a high-level idea, each file has a digest computed on it and the file and signature are added to the zip file. The vlei-verifier will validate each signatures vs. the digest of each file.
You can find a variety of test report files here.
For deployment history and version details of the reg-pilot-api and vlei-verifier services, see the DEPLOYMENTS.md
file.