Mokhtar Naamani 2f05da0c6d types v0.17.2 | 2 rokov pred | |
---|---|---|
.. | ||
bin | 3 rokov pred | |
config | 3 rokov pred | |
docs | 2 rokov pred | |
scripts | 3 rokov pred | |
src | 2 rokov pred | |
.eslintignore | 3 rokov pred | |
.eslintrc.js | 3 rokov pred | |
.gitignore | 3 rokov pred | |
.prettierignore | 3 rokov pred | |
README.md | 3 rokov pred | |
config.yml | 2 rokov pred | |
docker-compose.yml | 3 rokov pred | |
openapitools.json | 3 rokov pred | |
package.json | 2 rokov pred | |
tsconfig.json | 3 rokov pred |
The Joystream Distributor CLI package contains a set of commands that allow:
To see the list of all available commands and their flags / arguments, check out the commands documentation.
All the configuration values required by Joystream Distributor CLI are provided via a single configuration file (either yml
or json
).
The path to the configuration will be (ordered from highest to lowest priority):
--configPath
flag provided when running a command, orCONFIG_PATH
environment variable, orconfig.yml
in the current working directory by defaultAll configuration values can be overriden using environment variables, which may be useful when running the distributor node as docker service.
To determine environment variable name based on a config key, for example intervals.cacheCleanup
, use the following formula:
pascalCase
fieldnames to SCREAMING_SNAKE_CASE
: intervals.cacheCleanup
=> INTERVALS.CACHE_CLEANUP
__
: INTERVALS.CACHE_CLEANUP
=> INTERVALS__CACHE_CLEANUP
JOYSTREAM_DISTRIBUTOR__
prefix: INTERVALS__CACHE_CLEANUP
=> JOYSTREAM_DISTRIBUTOR__INTERVALS__CACHE_CLEANUP
In case of arrays or oneOf
objects (ie. keys
), the values must be provided as json string, for example JOYSTREAM_DISTRIBUTOR__KEYS="[{\"suri\":\"//Bob\"}]"
.
In order to unset a value you can use one of the following strings as env variable value: "off"
"null"
, "undefined"
, for example: JOYSTREAM_DISTRIBUTOR__LOGS__FILE="off"
.
For more envirnoment variable examples see the distributor-node
service configuration in docker-compose.yml.
For detailed configuration reference, checkout the config schema documentation.
To understand how the distributor node works in detail, checkout the node documentation.