The config.yaml I put in every update is generated fresh with
storagenode setup
The config.yaml I put in every update is generated fresh with
storagenode setup
Its not needed. The trust-cache.json
file gets auto downloaded every few mins with updated trusted sources.
storage2.monitor.reserved-bytes: 100 GB
So now we can set the free space limit?
Only if you enable the dedicated disk feature
storage2.monitor.dedicated-disk: true
Storj could create a config-default.yaml file next to config.yaml, with each new version installation. This way we would have the last version of it right on our nodes.
actually seems crazy smart to me.
You could just rename the existing config.yaml and run ‘storagenode config’ command. The result is a default config.
This is new to me. Do you need to stop the node? Is there anything else to put in that command? Shouldn’t be:
docker run storagenode config ?
or something like that?
docker exec -it storagenode storagenode config
would be enough. However, it would also try to open a text editor. If your run rootless, then you would be unable to install it in the container.