Skip to main content

Configuration

Networks functionality can be enabled by placing networks: into the configuration file.

For the node to be fully capable of participating in a network it needs to have pipelines functionality enabled.

Otherwise, node's web UI will only allow network configuration through Networks section. The node will not be able to deploy pipelines expected by the network.

Example:

node:
  id: server

errorReporting:
  allow: true

http:
  address: 127.0.0.1:8769

hubServer:
  authenticationByRequest:
    timeout: 5m
  accessTokens:
    client-1: client-1
    client-2: client-2

networks:

Default node carriers​

It is possible to configure carriers that node will receive every time it joins a new network.

  • defaultNetworkCarriers
    • carriers - array
      • optional address
        • ip - string
        • port - uint32
        • optional externalIp - string
      • optional interface - string
      • optional bandwidthPriority - uint32

Example:

defaultNetworkCarriers:
  carriers:
    - address:
        ip: "127.0.0.1"
        port: 3425
        externalIp: "192.168.0.55"
      interface: "eth0"
      bandwidthPriority: 100

Default blueprints​

NanoPing allows to predefine which network blueprints will be used as defaults in the configuration file.

To point to correct blueprint get a key, which can be found in the url.

  • defaultBlueprints
    • optional relay - string
    • optional relayClient - string
    • optional client - string

Example:

blueprint_key.png

defaultBlueprints:
  client: "d9a0e287-4abd-11f1-9002-9c6b008999fe"