The Target (modular) Architecture of openIMIS foresee several deployment possibilities and is installed "aside" a legacy installation. Aside may mean:
...
One clear limitation though: they are connected to the same database (thus if the patch requires database change, the backward compatibility of the change must be guaranteed).
DEMO Platform (TEMPORARY SOLUTION)
LEGACY_DNS: https://demo.openimis.org/
LEGACY_IP: 132.148.242.96
DATABASE_NAME: ??
LEGACY_SERVER: Windows 2012 R2
NEW_DNS: https://openimis.bluesquare.org/
NEW_IP: 18.197.14.226
NEW_SERVER: Ubuntu 18.04.02 LTS
frontend modules versions:
- openimis/fe-core@0.0.17
- openimis/fe-home@0.0.9
- openimis/fe-location@0.0.6
- openimis/fe-insuree@0.0.12
- openimis/fe-medical@0.0.6
- openimis/fe-product@0.0.2
- openimis/fe-policy@0.0.9
- openimis/fe-claim@0.0.14
- openimis/fe-claim_batch@0.0.2
- openimis/fe-admin@0.0.13
- openimis/fe-tools@0.0.10
- openimis/fe-profile@0.0.10
ibackend modules versions:
- openimis-be-core==0.0.13
- openimis-be-location==0.0.5
- openimis-be-medical==0.0.6
- openimis-be-product==0.0.2
- openimis-be-insuree==0.0.6
- openimis-be-policy==0.0.7
- openimis-be-contribution==0.0.1
- openimis-be-claim==0.0.13
- openimis-be-api_fhir==0.0.4
NEPALI "TEST" Platform:
LEGACY_DNS: http://imistest.hib.gov.np/
...
LEGACY_DNS: ??
LEGACY_IP: 132.148.151.32
DATABASE_NAME: openIMIS-demo-1.3.0
LEGACY_SERVER: Windows 2012 R2
...