Launch Cares
To Launch Cares only.
Last updated
To Launch Cares only.
Last updated
Cares on platform meant to work alongside with Disi. However, if you want to launch it alone it is possible
Steps are as follows:
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
called interoperability-layer-openhim
Add first file called under the folder created in the first step: openhimConfig.js
Copy the following code in that file:
Create another file called: openhim-import.json
Copy the following code in that file:
Now, we need to add the service that will import the configs.
Add the following the docker-compose.config.yml
file inside the importer
folder:
The openHIM config importer should be removed after importing, so we need to add the two following lines in the swarm.sh
script:
Finally, 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.
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:
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 services
down
for stopping the services
up
for bringing the services up
destroy
for removing the services