Configuration File

By using a configuration file, you can change the connection information. A configuration file is a JSON file as shown below;

{
  "hosts": ["https://localhost:9010/"],
  "fallback": true,
  "memebers":[
    "02dc2b9c7c3cd36f8cf8dbc5ecd4880d60079a3afe3156bc0bc863a7424f1e264a",
    "02fd35ds7c3cd36f8cf8dbc5ecd4880d60079a3afe3156bc0bc863a7743290823d"

  ],
  "clientCert": "\\node\\0.p12",
  "clientCertPwd": "<password>",
  "extensions":[{
      "name": "Miyabi.BLS"
    },
    {
      "name": "Miyabi.Binary"
    },
    {
      "name": "Miyabi.Asset"
    },
    {
      "name": "Miyabi.Entity"
    },
    {
      "name": "Miyabi.Contract"
    },
    {
      "name": "Miyabi.NFT"
    }],
  "timeoutperhost":"00:00:20",
  "retryperhost":"3"
}

The following table describes each configuration field:

Field	Description
hosts	Specifies Miyabi node host information. Multiple destination hosts can be set and the top of the list is used by default.
fallback	If multiple destinations are specified, CLI tries to connect one by one from the top of the list until it succeeds.
clientCert	Path to PKCS12 file that is used by admin commands.
clientCertPwd	Path to a password file containing the raw text password which is used by the PKCS12 file specified by clientCert.
members	The credentials of the nodes taking part in the consensus process
extensions	Specifies which modules to load. By default, all modules are loaded automatically and this field might not require any changes.
timeoutperhost	Maximum time for a request to wait from the host
retryperhost	Maximum number of retries a host can have before TimeoutPerHost is elapsed