41a9261069
``` > source config/example/node.env config/example/node.env: строка 14: /dns4/s02.neofs.devenv/tcp/8081: Нет такого файла или каталога config/example/node.env: строка 16: MSK: команда не найдена config/example/node.env: строка 35: 028f42cfcb74499d7b15b35d9bff260a1c8d27de4f446a627406a382d8961486d6: команда не найдена config/example/node.env: строка 48: https://rpc2.morph.fs.neo.org:40341: Нет такого файла или каталога config/example/node.env: строка 49: wss://rpc2.morph.fs.neo.org:40341/ws: Нет такого файла или каталога config/example/node.env: строка 53: https://rpc2.n3.nspcc.ru:30341: Нет такого файла или каталога ``` New implementation is still basic, but we don't need to parse any env file, just have a correct example. Signed-off-by: Evgenii Stratonikov <evgeniy@nspcc.ru> |
||
---|---|---|
.. | ||
node.env | ||
node.json | ||
node.yaml | ||
README.md |
Examples of correct configuration file structures
Here are files in all supported formats and with all possible configuration values of NeoFS applications. See node.yaml for configuration notes.
All parameters are correct, however, they are for informational purposes only. It is not recommended transferring these configs for real application launches.
Config files
- Storage node
- JSON:
node.json
- YAML:
node.yaml
- JSON:
Environment variables
- Storage node:
node.env