|0.1.5||Feb 7, 2023|
|0.1.4||Feb 7, 2023|
#215 in Testing
30 downloads per month
Quickly vet your releases for QA.
qvet has two main components:
web: The shiny dashboard UI. Most functionality is here.
api: A lightweight backend, used where secrets are required.
All data is stored in Github, there is no additional persistent store/database required.
Github App Configuration
- Commit statuses: Read and Write
- To read and set QA status
- Contents: Read only
- To read branches, commits and tags
Events (currently not required)
- To listen for a new tag (release) being created
- To listen for new commits being pushed to master
- To listen for QA statuses being updated
Start the two services in development/hot reload mode. Respectively:
cd web && npm install && npm run dev
cd api && cargo watch -x 'run -- --bind 0.0.0.0:3000'
qvet can run bundled in a single binary.
For convenience, this binary is available in a thin docker image wrapper.
To build a new release, run
./qvet-standalone/scripts/build.sh, which will produce an image named
This can then be invoked as follows:
docker run -d --rm --name ci-qvet --init -e GITHUB_CLIENT_ID -e GITHUB_CLIENT_SECRET -e QVET_COOKIE_KEY -p 39106:39105 qvet-standalone --bind 0.0.0.0:39105
||Github App Client Id||Required|
||random hexadecimal, 40 characters||Github App Client Secret||Required|
||random hexadecimal, 64 characters||qvet private cookie encryption||Optional. If unset, a random key will be generated at runtime.|