This repository contains the React AVO Client app front-end for the end user.
| Role | Handle / username |
|---|---|
| Principal/Owner | Bart Debunne bart.debunne@viaa.be |
| Lead Developer | Enzo Eghermanne enzo.eghermanne@studiohyperdrive.be |
| Lead Developer | Bert Verhelst bert.verhelst@studiohyperdrive.be |
| Developer | Benjamin Naesen benjamin.naesen@studiohyperdrive.be |
| Developer | Andry Charlier andry.charlier@studiohyperdrive.be |
Code Review:
The React AVO Client app will provide the following:
- Implementation of the React @viaa/components in screens for the end user
- Coupling with the NodeJS proxy for authentication & search
| QAS | PRD | |
|---|---|---|
| host | TODO | TODO |
NodeJS proxy w/Typescript and Express.js
- Client app: React
- Admin app: React
// TODO
Jenkins builds a docker image and uploads it to the viaa docker registry.
See postman collection (TODO add link)
Steps to deploy:
- Update package.json version to match release branch version
- Do
npm installor update the version of the package-lock.json file version - Extract translations
- Merge release branch into master
- This deploys to
qasif the integration tests succeed
- Add tag on master + push the tag (format: v1.1.1)
- Wait for build to succeed (eta 20min)
If the deploy completes successfully but the version on the server doesn't seem to update, this could be an issue with the image not automatically being selected by openshift
Steps:
- You can login to openshift
- Go to Deployments > avo2-client-qas
- Actions > edit at the top right
- Scroll down to Image Stream Tag and select the correct image in the dropdown on the right
- Save, wait for image to be deloyed
Note:
- the correct image should normally be the tag containing the environment name (eg: qas for qas environment)
- This image is automatically updated when a new deploy occurs
- When you select a different image than the env image, the auto updating behavior will not happen anymore