Docker Workflow for DTaaS
This document describes the building and use of different Docker files for development and installation of the DTaaS platform.
NOTE: A local Docker CE installation is a prerequisite for using Docker workflows.
Run
Follow the instructions in docker/README.md to spawn a localhost development
instance of DTaaS. It is an end-to-end testing of the current codebase
as it exists in the local git directory.
Publish Docker Images
Build and publish the docker images. This step is required only for the publication of images to Docker Hub.
This publishing step is managed
only by project maintainers. Regular developers can skip this step.
The DTaaS development team publishes reusable packages which are then put together to form the complete DTaaS application.
The packages are published on github, npmjs, and docker hub repositories.
The packages on github are published more frequently but are not user tested. The packages on npmjs and docker hub are published at least once per release. The regular users are encouraged to use the packages from npm and docker.
A brief explanation of the packages is given below.
| Package Name | Description | Availability |
|---|---|---|
| dtaas-web | React web application | docker hub and github |
| libms | Library microservice | npmjs and github |
| docker hub and github | ||
| runner | REST API wrapper for multiple scripts/programs | npmjs and github |
React Website
To tag version 0.3.1 for example, use
To test the react website container on localhost, please use
Library Microservice
The Dockerfile of library microservice has VERSION argument.
This argument helps pick the right package version from http://npmjs.com.
To tag version 0.3.1 for example, use
To test the library microservice on localhost, please use