NodeVerify is used to perform some generic work in testing orchestrators performance and overhead.
1.7K
NodeVerify is used to perform some generic work in testing orchestrators performance and overhead.
The following environment variables must exist in order for the API to work.
3005hashmesha256A status endpoint is available once launched:
/v1/status - Will return a status of running if successful.
"status": "running"/v1/guidhash - Will create a new guid userid, hash that userid, and return the payload.
/v1/guidhash/:userid - Will hash the :userid provided, and return the payload.
To launch this API with docker, use the following. You may swap in a docker environment file if you choose, replacing values with real values.
Provided cross post on github packges. In addition, this repository includes an example Github Actions workflow for building multiple os images and using manifest to join them to one tag.
From Dockerhub:
docker run -d -p 3005:3005 jhardison/nodeverify
or
docker run -d -p 3005:3005 jhardison/nodeverify:latestlinux
From Github:
docker run -d -p 3005:3005 ghcr.io/jmhardison/nodeverify
or
docker run -d -p 3005:3005 ghcr.io/jmhardison/nodeverify:latestlinux
From Dockerhub:
docker run -d -p 3005:3005 jhardison/nodeverify
or
docker run -d -p 3005:3005 jhardison/nodeverify:latestwindows
From Github:
From Github:
docker run -d -p 3005:3005 ghcr.io/jmhardison/nodeverify
or
docker run -d -p 3005:3005 ghcr.io/jmhardison/nodeverify:latestwindows
latest - provides the latest linux (or) windows distribution.latestwindows - provides the latest windows distributionlatestlinux - provides the latest linux distributionContent type
Image
Digest
sha256:699bee318…
Size
94.2 MB
Last updated
almost 3 years ago
docker pull jhardison/nodeverify