We use HoCon (see introduction or full specification for details) as our main configuration format. Lightbend config library is used for parsing configuration files - you can check documentation for details on conventions of file names and merging of configuration files.
Following Nussknacker specific rules apply:
nussknacker.config.locationssystem property (
NUSSKNACKER_CONFIG_FILEenvironment variable for Docker image) defines location of configuration files (separated by comma). The files are read in order, entries from later files can override the former (using HoCon fallback mechanism) - see docker demo for example:
- defaultUiConfig.conf contains defaults for Nussknacker designer
config.override_with_env_varsis set to true, so it’s possible to override settings with env variables
It’s important to remember that model configuration is prepared a bit differently. Please read Model configuration for the details.
Nussknacker configuration is divided into several configuration areas, each area addressing a specific aspect of using Nussknacker:
- Designer configuration
- Scenario types configuration
- Deployment manager/executor configuration
- Model configuration
Designer configuration contains all settings for Nussknacker designer - e.g. web application ports, security, various UI settings.
One Nussknacker designer deployment may be used to create various Scenario types which:
- Deployed with various deployment managers to e.g. different Flink clusters
- Using different components and model configurations
See development configuration (used to test various Nussknacker features) for an example of configuration with more than one scenario type.
Diagram below presents main relationships between configuration areas.