Versionen im Vergleich

Schlüssel

  • Diese Zeile wurde hinzugefügt.
  • Diese Zeile wurde entfernt.
  • Formatierung wurde geändert.

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

...

You can follow along Providing a custom Plugin for the UM Cloud to create an empty Plugin, test it locally and have it included in your UM Cloud instance.

Manipulating the data model (aka

...

editing “additional.

...

attributes”)

In a UM Cloud environment it is generally not a good idea to overwrite the global cmsbs-conf/additional.attributes file as it is provided by Pinuts and might (need to) be updated in the course of a UM update. Instead, you can create incremental changes by putting cmsbs-conf/conf.d/*.attributes files into your Plugin.

...

Please remember that adding new primary attributes or adding columns to an already existing TABLE attribute require providing Automating Database Schema Updates.

Setting global configuration options (aka editing “cmsbs.properties”)

Likewise, you must not override the global cmsbs-conf/cmsbs.properties file in a UM Cloud environment. But similarly you can make incremental changes by putting cmsbs-conf/conf.d/*.properties files into your Plugin.

You can also put your properties files into well-known directories to have them take effect only in a specific UM environment (i.e. test, staging or prod):

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

  • env

...

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

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

Example

Ladereihenfolge der Konfigdateien

...