Local configuration files

Besides environment variables, the Node can be configured using local configuration files. Note that these configuration files require you to have access to the root-folder of the Node. All configuration files are located in the 'data' sub-folder in the root-folder of the Crosser Node. Configuration files might evolve over time with Node updates.All changes in configuration files will only be applied once the flow runtime is restarted.

appsettings.json

This file controls flow runtime settings for the actual application itself like the log-level, communication-interval to the Flow manager, the path to the Python environment (only relevant for Windows setups), and more.

No modifications are required unless Python is needed on Windows installations.

credentials.json

This file holds the flow runtime Name, NodeID, organization and hashed credentials for the flow runtime. This file is created once the flow runtime connects to the Flow manager for the first time. Do not manually adjustment this file.

endpoints.json

This file establishes settings for the flow runtime's exposable endpoints: MQTT and HTTP, as well as the base-URL which you might want to adjust in case you have an on-premise installation of the flow manager. This is also the place where you can specify your proxy settings in setups where you break-up the SSL connection between the flow runtime and the flow manager.

httpconfiguration.json

As the name suggests, this file controls the exposable HTTP endpoint.

mqttconfiguration.json

As the name suggests this file controls the exposable MQTT Broker.