💉
CARES on Platform
  • Getting started
  • Overview
    • General Structure
    • The Source: Platform
    • A Custom package
  • Design & Architecture
    • General Architecture
    • References from Platform
    • Flow of the data
    • Customized stack
  • Launching & Local Testing
    • Start overriding the config
    • Launch Cares
    • Launch Cares & Disi
    • Dev & Prod mode
    • Test the stack
  • Troubleshooting & Monitoring
    • Using the Monitoring package
    • Locate the issue
    • Backup & Restore
  • Deployment
    • Local deployment
    • Deploy on a Remote Server
  • Postman Collections
  • Sante MPI Configuration
Powered by GitBook
On this page
  1. Deployment

Deploy on a Remote Server

To deploy on a remote server, you should follow the two steps:

1. Edit the .env.* and edit the following fields:

- OPENHIM_CORE_MEDIATOR_HOSTNAME= <OPENHIM_SUBDOMAIN> (default localhost) - DOMAIN_NAME= <DOMAIN_NAME> of remote server - SUBDOMAINS= <SUBDOMAINS OF ALL EXPOSED SERVICES>

You may need to update the memory and CPU limit according to the server.

Example: 

OPENHIM_CORE_MEDIATOR_HOSTNAME=openhimcomms.domain.com
DOMAIN_NAME=domain.com
SUBDOMAINS=openhimcomms.domain.com,openhimcore.domain.com,openhimconsole.domain.com,kibana.domain.com,reports.domain.com,superset.domain.com,santempi.domain.com,santewww.domain.com

2. Run the following command to deploy Cares and Disi: 

DOCKER_HOST=ssh://<username>@<host> ./deploy-local-combo.sh init

With:

  • username: is the user of the remote server

  • host: is the domain name or the IP address of the remote server.

PreviousLocal deploymentNextPostman Collections

Last updated 2 years ago