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).

RELEASE (TEMPORARY SOLUTION)

The release.openimis.org installation is NOT a standard openIMIS installation in several major aspects:

• because of Windows 2012 compatibility issues, it is not running within dockers
  • React app is served from IIS
  • Django app is deployed as a separate Windows service
  • openResty gateway is deployed as a separate Windows service, with a corresponding 'fake' app on IIS (to establish reverse proxy rules)
• the application is deployed from the source code, from the release github branch (i.e. not from published components versions from npm or pypi)

The only objective of this setup is to enable acceptance testing for the release but should not be reproduced for production usage.

Image Added

Some highlights:

• the C:\Windows\System32\drivers\etc\hosts file has an entry for release.legacy.openimis (bound to 127.0.0.1) in order to make release.legacy.openimis IIS app routable from the OpenResty gateway
• the (react) front is built (yarn build) from C:\new_OpenIMIS_TEST\frontend\openimis-fe-* modules, linked (yarn link) into C:\new_OpenIMIS_TEST\frontend\openimis-fe_js
• the (django) backend is served from C:\new_OpenIMIS_TEST\backend\openimis-be_py\launch.bat, which uses the C:\new_OpenIMIS_TEST\backend\openimis-be_py\venv virtual env in which all C:\new_OpenIMIS_TEST\backend\openimis-be-*  modules are linked (pip install -e ...)

DEMO Platform (TEMPORARY SOLUTION)

...

LEGACY_DNS: ??

LEGACY_IP: 132.148.151.32

DATABASE_NAME: openIMIS-demo-1.3.0

LEGACY_SERVER: Windows 2012 R2

...