Seitenvergleich

In your UM Cloud installation you cannot just SSH into your machine and edit one of the familiar configuration files (cmsbs.properties, additional.attributes etc.) to update certain global settings, modify the data model or add custom CSE plugins.

...

• env/test/cmsbs-conf/conf.d/

• env/staging/cmsbs-conf/conf.d/

• env/prod/cmsbs-conf/conf.d/

Example

Ladereihenfolge der Konfigdateien

Unsere ganz vorn mit _pi.*

Adding and overwriting configuration files

When a Cloud UM is deployed, configuration files will be copied together in a certain order, with files of the same name being overwritten.

1. The whole cmsbs-conf/ directory is pre-populated by the familiar UM installer that is run automatically.

2. Certain files are added to or overwritten in cmsbs-conf/ to adapt the UM to the Cloud environment in general and to prepare it for the specific customer.

3. Your custom UM Plugins will be deployed last so they could – in principle – override each and every file that pre-exists:

   1. First, cmsbs-conf is copied on top of the existing directory,

   2. and second, env/<environment>/cmsbs-conf/ is in turn copied on top.

Loading order of configuration files

When the UM starts, configuration files will be loaded and evaluated in the following order:

1. cmsbs-conf/cmsbs.properties

2. cmsbs-conf/conf.d/*.properties (in alphanumerical order of the respective file names)

The same applies to attribute model configuration files:

1. cmsbs-conf/additional.attributes

2. cmsbs-conf/conf.d/*.attributes (in alphanumerical order of the respective file names)

All configuration files in cmsbs-conf/conf.d/ that are provided by Pinuts share the same file name prefix _pi. and thus will be evaluated first.