This guide applies to command-line application users. Gui users can safely ignore the use of config files - Gui handles basic configuration automatically. It is also worth noting that some of our guides show configuration file settings and other guides show startup command flags.
Configuration File Locations¶
All of the Drep software, when started, reads from a configuration file to determine which settings it should enable/disable/set during that initial load. All of the command line startup flags
(e.g. drep --loglevel 5) can be replaced by settings within the appropriate configuration file
(e.g. drep --loglevel 5 could be replaced by loglevel:1 in config.json file of app home directory).
These configuration files are located within the application home directory of the application. The location of these default home directories for Windows, macOS, and Linux are listed below:
|OS||drep App Directories|
Each of these folders is allowed its own
config.json file, . Please also note that the
drep home directories are automatically created when each application is first launched.
The drep installation method automatically creates configuration files, with the minimum configuration settings already enabled.
The Manual Installation method includes sample configuration files within the .zip/.tar.gz. It is recommended to copy these config files into the appropriate directory described above, and rename them to remove ‘sample-‘. These files have many settings commented out (comments are not read by the program during runtime) so all of these settings are effectively disabled.
Startup Command Flags¶
A majority of the settings you are able to set via the configuration file can also be passed to the application as parameters during launch. For example, the following OS-specific commands would open
drep for Mainnet use, an alternative to using
--loglevel 5 in your config file:
Windows: drep.exe --loglevel 5 macOS: ./drep --loglevel 5 Linux: ./drep --loglevel 5
The above example would first look to the
drep configuration file for settings and then look to the executable command to enable the loglevel setting.