This section describes BLOCd daemon starting process with correct arguments enabling access to the BLOCd HTTP RPC API, the BLOCd JSON RPC API and BLOCd Command Inline Options
BLOCd can accept settings through a configuration file and/or command line: -config-file=BLOC.conf
Almost all of the command line options can be defined through the configuration file. If a parameter is defined in the config and was also indicated in the command line, two behaviors are possible:
- If the parameter accepts one value only (e.g.,
rpc-bind-ip), the command line value will be used, since it has a higher priority
- If the parameter accepts several values (e.g.,
add-priority-node), then command line and configuration file values will be merged
- If some of the options are not defined in the config, the default values will be applied
- By default config file's name is BLOC.conf, which is located in the binaries folder
- You may adjust the destination to the file via
--config-file option in the command line.
- Config files, where used, now use JSON formatted files instead of INI
- Config files will be automatically upgraded to JSON and overwritten on first use
- Config file's path is relative to current working directory, not server root.
Make sure you visit this guide to get you started with BLOCd Arguments in no time to learn how to create your custom config file and launch BLOCd using it. Then you can use this page to browse the different BLOCd Command Line Argument available.
Once you have selected all your options, place the file next to BLOCd and start it like this:
Windows: : BLOCd.exe --config-file=myconfig.conf
Mac and Linux : ./BLOCd --config-file=myconfig.conf
You are now ready to use the BLOCd HTTP RPC API the BLOCd JSON RPC API and/or the BLOCd Command Inline Options