Current Status
Future Infrastructure (in planning)
Principles
consistent production lines
Minimize admin costs
optimize performance
data integrity
Server-Options
assumption:
one server = one IP, one operating system (LINUX WINDOWS NAP LOCAL )
one cell = one instance on a server
no distributed resources
Application / Line | Develop | Release / Integration | Quality Assurance | Demo | Training |
|---|---|---|---|---|---|
github branches | feature | develop | release | main | main |
used for | developer test | integration test | user acceptance test | current stable | customized demos / trainings |
openIMIS Legacy | LOCAL | WINDOWS 2 | WINDOWS 2 | WINDOWS 4 | WINDOWS 5 |
openIMIS Modular | LOCAL | LINUX 2 | LINUX 2 WINDOWS 2 | LINUX 4 | LINUX 5 |
openIMIS DB | LOCAL | WINDOWS 2 | WINDOWS 2 | WINDOWS 4 | WINDOWS 5 |
DHIS2 w/ oI connector | LOCAL | LINUX 2 | LINUX 2 | LINUX 4 | LINUX 5 |
DHIS2 DB | LOCAL | LINUX 2 | LINUX 2 | LINUX 4 | LINUX 5 |
OpenHIM | LOCAL | LINUX 2 | LINUX 2 | LINUX 4 | LINUX 5 |
OpenMRS | NAP | NAP | LINUX 2 | LINUX 4 | LINUX 5 |
BAHMNI | NAP | NAP | LINUX 2 | LINUX 4 | LINUX 5 |
FHIR (HAPI FHIR) | NAP | NAP | LINUX 2 | LINUX 4 | LINUX 5 |
PFSENS (Firewall etc) | FREE BSD | ||||
Discussion
look at loads
Modular doesn’t need windows server
lines:
develop: own computers, online DB for testing
training: several instances on one server (same IP, different ports/ subdomains)