Skip to main content
Version: 4.x

Applications

Overview​

Application configuration stores the key-value settings of an application per environment; other applications obtain all of them by depending on that application.

Application configuration

  • Typical example: application B calls an endpoint of application A, so B needs the IP or domain of A. Keep the address in the configuration of A and let B depend on A instead of copying it into B, because C / D / E / F may need it too and duplicating it everywhere is hard to maintain.

Fields​

  • Name / Identifier / Description: the same data as the applications under Deployment / Applications; the identifier is the prefix of the generated keys.

Dependencies​

Click Dependencies in the row of an application to select the applications and services it depends on. Afterwards the application obtains all values of those applications and services (through the API or as environment variables during deploys).

Dependencies

Notes​

  • In 4.0 application values no longer have a public / private type: all values of an application are handed to the applications that depend on it, so keep sensitive values out of applications that others depend on.
  • The configuration center exists to manage differences between environments. Values that are identical in every environment can simply be hard-coded.
  • Click Config to manage the values of the application, see Configuration.