The default DefraDB directory is $HOME/.defradb
. It can be changed via the --rootdir CLI flag.
Relative paths are interpreted as being rooted in the DefraDB directory.
Store can be badger or memory. Defaults to badger
.
- badger: fast pure Go key-value store optimized for SSDs (https://github.com/dgraph-io/badger)
- memory: in-memory version of badger
The number of retries to make in the event of a transaction conflict. Defaults to 5
.
Currently this is only used within the P2P system and will not affect operations initiated by users.
The path to the database data file(s). Defaults to data
.
Maximum file size of the value log files.
Address of the HTTP API to listen on or connect to. Defaults to 127.0.0.1:9181
.
The list of origins a cross-domain request can be executed from.
The path to the public key file for TLS / HTTPS.
The path to the private key file for TLS / HTTPS.
Whether P2P networking is disabled. Defaults to false
.
List of addresses for the P2P network to listen on. Defaults to /ip4/127.0.0.1/tcp/9171
.
Whether PubSub is enabled. Defaults to true
.
List of peers to boostrap with, specified as multiaddresses.
https://docs.libp2p.io/concepts/addressing/
Enable libp2p's Circuit relay transport protocol. Defaults to false
.
https://docs.libp2p.io/concepts/circuit-relay/
Log level to use. Options are info
or error
. Defaults to info
.
Log output path. Options are stderr
or stdout
. Defaults to stderr
.
Log format to use. Options are text
or json
. Defaults to text
.
Include stacktrace in error and fatal logs. Defaults to false
.
Include source location in logs. Defaults to false
.
Logger config overrides. Format <name>,<key>=<val>,...;<name>,...
.
Disable colored log output. Defaults to false
.
Path to store encrypted key files in. Defaults to keys
.
Disable the keyring and generate ephemeral keys instead. Defaults to false
.
The service name to use when using the system keyring. Defaults to defradb
.
Keyring backend to use. Defaults to file
.
file
Stores keys in encrypted filessystem
Stores keys in the OS managed keyring