💉
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
  • Enable DEV mode
  • Accessible services in DEV mode locally
  • DEV vs PROD
  1. Launching & Local Testing

Dev & Prod mode

Access services and the difference between both modes.

PreviousLaunch Cares & DisiNextTest the stack

Last updated 2 years ago

how to access different components in dev mode vs in prod mode

Enable DEV mode

To enable dev mode and as the Platform CLI docs mentioned, all you need to do is to add --dev if it is not already there to the commands as follows:

./deploy-local.sh init --dev

or

./deploy-local-combo.sh init --dev

Accessible services in DEV mode locally

Running in Dev mode locally will allow you to access the following services:

  • Openhim: or

  • Kafdrop: or

  • Clickhouse: or

  • Superset: or

DEV vs PROD

The following services will not be accessible in Prod mode:

  • Kafdrop

  • Clickhouse

http://127.0.0.1:9000
http://localhost:9000
http://127.0.0.1:9013
http://localhost:9013
http://127.0.0.1:8124/play
http://localhost:8124/play
http://127.0.0.1:8089
http://localhost:8089