💊
DISI on Platform
  • Overview
  • Getting Started
  • Deployment
    • Local Deployment
    • Remote deployment
  • Troubleshooting and Monitoring
    • Monitoring
    • Locating Issues
    • Backup and Restore
  • Postman Collections
  • Sante MPI Configuration
Powered by GitBook
On this page
  • Hardware Requirements
  • Deploying

Deployment

PreviousGetting StartedNextLocal Deployment

Last updated 2 years ago

This project is an implementation of the generic project. It makes use of the Platform's base packages and its own custom packages.

You can take a look at docs, as well as docs to understand the basics of the CLI and the packages used in this project.

Hardware Requirements

This project is resource intensive. A machine with at least 24G RAM is required. Performance issues may be experienced with less.

Deploying

This project can be deployed in Single or Clustered mode. This is done by setting the environment variable CLUSTERED_MODE to either true or false in the .env file matching the deploy script being used. For example the env file for the script deploy-local.sh is .env.local.

Configuration

The services can be configured via environment variables. Below is a list of the available deploy scripts and their .env files.

  • deploy-local.sh .env.local

  • deploy-qa.sh .env.qa

  • deploy-st.sh .env.stg

Below is a list of links to the environment variables for each service

  • Fhir Datastore - Hapi FHIR

  • Interoperability Layer - OpenHIM

  • ​Analytics Datastore - Elasticsearch

  • Dashboard Visualiser - Logstash

  • ​Dashboard Visualiser - Jsreport

  • ​Client Registry - Sante MPI​

  • Message Bus - Kafka

  • ​NGINX (reverse proxy)

  • OpenHIM mediators - MPI-checker​

  • OpenHIM mediators - MPI-updater

  • Monitoring (Grafana and Prometheus)

Platform CLI
Platform
Jembi Platform