Local Development Deployment
Profile dev-local-3nodes
This deployment profile deploys 3 MedCo nodes on a single machine for development purposes. It is meant to be used only on your local machine, i.e. localhost
. The tags of the docker images used are all dev, i.e. the ones built from the development version of the different source codes. They are available either through Docker Hub, or built locally.
MedCo Stack Deployment (except Glowing Bear)
First step is to clone the medco-deployment
repository with the correct branch. This example gets the data in the home directory of the current user, but that can be changed.
Next step is to build the docker images:
Note that instead of building the dev docker images locally, it is possible to download them from Docker Hub by using docker-compose pull
, but there is no guarantee on the current status of those images are they are automatically built.
Next step is to run the nodes. They will run simultaneously, and the logs of the running containers will maintain the console captive. No configuration changes are needed in this scenario before running the nodes. To run them:
Wait some time for the initialization of the containers to be done (up to the message: “i2b2-medco-srv… - Started x of y services (z services are lazy, passive or on-demand)”), this can take up to 10 minutes. For the subsequent runs, the startup will be faster.
Glowing Bear Deployment
First step is to clone the glowing-bear
repository with the correct branch.
Glowing Bear is deployed separately for development, as we use its convenient live development server:
Note that the first run will take a significant time in order to build everything.
In order to stop the containers, simply hit Ctrl+C
in all the active windows.
Keycloak Configuration
Test the deployment
Last updated
Was this helpful?