...
Metadata configurations get loaded through the initializer module(opens in a new tab) in O3. The initializer module, or Iniz for short, is a module that allows implementers to load metadata into their OpenMRS instances through JSON files. The various configuration files that ship with O3 are located in the distro/configuration directory of the distro reference application config(opens in a new tab) repository. The initializer module supports loading a wide variety of data and metadata types, including but not limited to:
...
For more information on how to configure your O3 instance using the initializer module, read the Iniz repository's README(opens in a new tab).
Configuring individual frontend modules
...
Typically, you're going to need to make multiple configuration overrides to various frontend modules. The canonical way to do this is to create a JSON configuration file that lives on your server. You can then point your SPA to this configuration file by specifying its URL in the SPA build configuration file. An example of such a config file is the Ozone Cambodia config file(opens in a new tab). Each key in the config file corresponds to a frontend module. The value of each key is an object containing the configuration properties that you want to override for that module. These properties correspond to whatever properties are defined in the module's config schema.ℹ️
| Info |
|---|
O3 loads frontend modules on demand. This means you'll only see a module's configuration properties in the implementer tools if the module itself has been loaded. If you're only seeing default keys like "Display conditions" and "Translation overrides" in a module config schema in the implementer tools, it means the relevant module likely hasn't loaded yet. To view configuration for modules related to a specific feature, like the order basket, navigate to that section of the application (e.g., the Patient Chart). Once the module loads, you'll see all its configurable properties in the implementer tools. |
Distro-level configuration
...
The distro.properties file is a configuration file that describes the backend modules that make up your distribution. The reference application's default distro.properties file lives here(opens in a new tab). The most important things to include in the distro.properties are:
...
The SPA build configuration is a JSON file that allows you to specify various configuration properties that get passed to the frontend modules during the build process. The SPA build configuration file is located in the frontend directory of your distro. The reference application spa-build-config file lives here(opens in a new tab).
The SPA build configuration file is used to specify the following properties:
...