This is an internal documentation. There is a good chance you’re looking for something else. See Disclaimer.

Set Application Properties

How to Set Properties

Primary ways to set properties:

  • During development create customer/${CUSTOMER}/etc/application-development.properties.

  • In production, use Ansible’s env variable. If available, set the corresponding Ansible variable listed in Available Application Properties instead.

  • Changes needed in production and development, commit to customer/${CUSTOMER}/etc/application.properties

More Ways to Set Properties

How/Where

Use cases

Command line: java -Dproperty=value

  • Development: options that should be enabled for all customers

  • Production: used when settings need to be overriddenduring DB refactoring.

customer/${CUSTOMER}/etc/application.properties [1]

  • Hardcoded setting which are applied during development and in production.

customer/${CUSTOMER}/etc/application-development.properties [1]

  • Development: options that should be enabled for a single customer locally only.

Environment variable: property=value

  • Docker: used to set properties when running in Docker (Build Nice Docker Image)

  • OpenShift: may be used to enable setting temporally for debugging:

    oc set env dc/nice property=value

    Removal:

    oc set env dc/nice property=-

    Ansible will overwrite any changes on next run.

Ansible config.yml/global.yml

  • Production: used to set properties on Openshift. In the background, Ansible sets the corresponding environment variables.

Footnotes