The different system that we use at PSI are accessible via URL across the different domains that the digital initiative PSI’s DHM manages. The intention of this page is to document the use of those URLs, and the naming conventions for the related sub-domains.
...
This the the default domain for all our systems, except DHIS2 (see next). Acquired in early 2023, we plan by the end of 2024 to transition ALL systems to the new URL.
Each system is represented by its name as the sub-domain, and an suffix when appropriate.
sub-domain | Type (see /wiki/spaces/DHM/pages/13271088) | Examples |
|---|---|---|
system name | When only the system name is shown, it represents the production environment | RapidPro keycloak |
system_name-.dev | the use of the suffix “-dev” denotes that the URL ifor the development /wiki/spaces/DHM/pages/13271088 of the related system. ALL systems that involve data capture (support create/update operations) are expected to have a development environment. | RapidPro-.dev |
system_name-.qa | the use of the suffix “-qa” denotes that the URL if for the Quality Assurance (testing) /wiki/spaces/DHM/pages/13271088 of the related system. MOST systems that involve data capture are expected to have a QA environment. QA environments are not required for superset or keycloak. | RapidPro-.qa
|
system_name-.stage | the use of the suffix “-stage” denotes that the URL if for the staging /wiki/spaces/DHM/pages/13271088 of the related system. MOST systems are expected to have a staging environment Staging environments are not required for superset or keycloak | RapidPro-.stage
|
...