DHIS2 configurations are created and modified on designated development environemnt/testing environment. Only after a full testing

When your DHIS2 configuration has been fully developed and tested and passed UAT, you should plan the deployment to production

This text should include

• Purpose

• Scope

• Pre-requisites

• Workflow (if applicable)

See also

text cycle, and with the final approval from the product owner during UAT, they can be moved to a production environment.

Moving a configuration

Moving a configuration (DHIS2 Program or Dataset) consist in obtaining an export configuration file in the form of a JSON file from the /wiki/spaces/DHM/pages/13271088, to be subsequently imported into the /wiki/spaces/DHM/pages/13271088.

...

Metadata export

You can export a DHIS2 configuration by using the build-in metadata export, with dependancies, or PSI’s Program Configuration App (PCA). If you use the build-in metadata export, you will need to ensure that you exclude sharing data, Org Unit assignments and any other UIDs that may not exist in the production server. If you use the PCA, simply select ‘clean export’, option that produce a file that can be imported into any server.

Metadata import

Very few users have the rights to import a metadata file into PSI’s production environment. You should test your metadata file in either PSI’s DHIS2 Clone or Staging /wiki/spaces/DHM/pages/13271088. If your program or dataset perform adequately, you should submit a request ticket to PSI’s help desk with the request “DHIS Production Deployment”

Data move

Normally, there is no need to move data from a testing/staging.

See also

Testing DHIS2 configurations and apps

Moving a DHIS2 Configuration to Production (Deployment)

Versions

...