See Use Cases and related docs
To enter test data, visit the dev version linkedtrust Dev
The frontend is fully working with Jenkins CI/CD Integration The logs can be found on jenkins last build And for Auth Details to the pipeline, kindly refer to vault jenkins logins, this creds would help you to gain access into the CI/CD pipeline and figure out why the test didn't run as it should, and also review the console outputs to figure out what the issue might be.
For SSH Access into the dev server, kindly refer to this creds in the vault dev server ssh creds this would help you ssh into the dev server
NB: The production version of this is available on live.linkedtrust.us
git clone https://github.com/Whats-Cookin/trust_claim.git
cd trust_claim
yarn devand connect to localhost:3000
To run in a new location you must set these environment variables i.e inside a .env file in the root directory
VITE_GITHUB_CLIENT_ID=[...]
VITE_BACKEND_BASE_URL=http://localhost:9000
VITE_CERAMIC_URL='http://13.56.165.66/'NB: This is a critical action !!!! To avoid having to run the back end you may point to the live backend BUT DO NOT WRITE JUNK TO IT
VITE_CERAMIC_URL='https://ceramic.linkedtrust.us/'
VITE_BACKEND_BASE_URL='https://live.linkedtrust.us'
VITE_DID_PRIVATE_KEY='...' in vault [DID PK](https://vault.whatscookin.us/app/passwords/view/0a1b11f4-03be-40e8-bda9-59791526967d)