Launch Cares
To Launch Cares only.
Cares on platform meant to work alongside with Disi. However, if you want to launch it alone it is possible 🎉
Steps are as follows:
Add OpenHIM configs
Because Cares-on-platform meant to work with DISI, and DISI have already configured openHIM. We didn't include openHIM configs so you should add it:
Create a folder under
importer
calledinteroperability-layer-openhim
Add first file called under the folder created in the first step:
openhimConfig.js
Copy the following code in that file:openhimConfig.jsCreate another file called:
openhim-import.json
Copy the following code in that file:openhim-import.jsonNow, we need to add the service that will import the configs. Add the following the
docker-compose.config.yml
file inside theimporter
folder:docker-compose.config.ymlThe openHIM config importer should be removed after importing, so we need to add the two following lines in the
swarm.sh
script:swarm.shFinally, as we don't have santeMPI in Cares, we will need the routing proxy to send the events to hapi-fhir, so it is imperative to add the hapi-proxy in the list of the dependencies of package-metadata.json in cares-on-platform:
Now, you should configured openHIM successfully.
Edit & check your Environment Variables
To launch Cares only, we're going to use .env.local file.
This file is initialized and have default values to work in single mode locally.
Please make sure you go through it and not forget to update the variables that should be updated.
Example: in single mode, the instances should have a value = 1 also Mongo and Postgres URLs should ping to one host:
Launch Cares
In this section, we're assuming that you already followed the steps in Getting started page.
In that case, to to launch cares all you have to do is to run the command:
./deploy-local.sh init
The following options can be passed to the ./deploy-local.sh
command:
init
for initializing the servicesdown
for stopping the servicesup
for bringing the services updestroy
for removing the services
Last updated