Skip to main content
Version: 1.7


The Docker image and the binary distribution contain minimal working configuration file, which is designed as a base for further customizations using additional configuration files. This file is not used by the Helm chart, which prepares its own config file.

Configuration areas

Nussknacker configuration is divided into several configuration areas, each area addressing a specific aspect of using Nussknacker:

  • Designer configuration (web application ports, security, various UI settings),
  • Scenario Types configuration, comprising of:

The Scenario Type is a convenient umbrella term for a particular Deployment Manager configuration and the associated model configuration. Diagram below presents main relationships between configuration areas.

Configuration areas

Let's see how those concepts look in fragment of main configuration file:

# Designer configuration 
environment: "local"

# Each scenario type is configured here
scenarioTypes {
"scenario-type-1": {
# Configuration of DeploymentManager (Flink used as example here)
deploymentConfig: {
type: "flinkStreaming"
restUrl: "http://localhost:8081"
# Configuration of model
modelConfig: {
classPath: ["model/defaultModel.jar", "model/flinkExecutor.jar", "components/flink"]
restartStrategy.default.strategy: disable
components {

It is worth noting that one Nussknacker Designer instance may be used to work with multiple Scenario Types which:

  • can be deployed with various Deployment Managers to e.g. different Flink clusters
  • use 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.

Environment variables

Environment variables are described in Installation guide, they are mostly helpful in the docker setup.


  • 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.
  • nussknacker.config.locations Java system property (CONFIG_FILE environment 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:
  • If config.override_with_env_vars Java system property is set to true, it is possible to override settings with env variables. This property is set to true in the official Nussknacker docker image.

It’s important to remember that model configuration is prepared a bit differently. Please read model configuration for the details.