Configuration
At its core, the Infernet Node operates according to a set of runtime configurations. Parameterized in config.json
, these configurations enable node operators to flexibly configure the functionality of a node.
While some configurations have sane defaults and do not need modification, it is useful to understand the implications of each option to configure your node to your unique application and use case.
Initializing config.json
Out-of-the-box, we provide a default config.sample.json
(opens in a new tab) as an example starting point that you can copy and modify:
# Copy and modify sample config
cp config.sample.json config.json
vim config.json
Versioning
New versions of the Infernet Node typically modify the exact configuration parameters available. To see the configuration parameters for a specific version, select the version from the tabs below.
We always recommend using the latest version of the Infernet Node, as it contains the most recent features and bug fixes.