Generally, every parameter set be cli flag used by akash can be also set via environment variable. Use following rule of binding flag to the corresponding environment variable
- every dash
-
must be replaced with underscore_
.--
prefix must not be accounted! - make all characters capital case
- add prefix
AKASH_
to the result
for example flag --keyring-backend
binds to AKASH_KEYRING_BACKEND
environment variable
The precedence is defined in the table below. 0 means highest priority
Priority | Type |
---|---|
0 | Environment variable |
1 | Flag |
2 | Config file |
3 | Default value |
Example below shows value precedence for --keyring-backend
parameter.
- use default value set to
os
akash tx deployment create ...
#keyring-backend=os is used
- use value set by flag
--keyring-backend=file
akash tx deployment create --keyring-backend=file ...
#keyring-backend=file is used
- use value set by environment variable
AKASH_KEYRING_BACKEND=test
AKASH_KEYRING_BACKEND=test akash tx deployment create --keyring-backend=file ...
#keyring-backend=test is used
|Name|Flag|Description|
|---|---|
|AKASH_VERSION
|Akash version to install for your network. See here.|
|AKASH_NET
|Akash network configuration base URL. See here.|
|AKASH_ACCOUNT_ADDRESS
|The address of your account. See here.|
|AKASH_NODE
|Akash network configuration base URL. See here.|
|AKASH_KEYRING_BACKEND
|Keyring backend to use for local keys. See here|