Currently the "openlmis/requisition-refui" docker image is targeted for developers to use locally. In order to run requisition UI Module with Requisition and Auth microservices, a developer has to run requisition-ui, build it with "grunt build" and then start the application using docker-compose-prod.yml file which has following volume defined:
A production image should be created and used so that it is possible to run requisition-refui along with other microservices correctly, using openlmis-blue repository, without need to build the code locally. "doker-compose-prod.yml" file should not force the inclusion of the requisition or auth docker image.
Requisition-UI can be run separately on it's own (without any other microservices) using developer docker image.
Requisition-UI can be run with other microservices using production docker image and openlmis-blue repository, without need to build the code locally.
Both Requisition-UI production and developer docker images are updated when Jenkins build is triggered.