But updater needs to update itself anyway. But it can’t if its services name is different from default.
So this is endless circle.
And updater not neccesarily needs to update every node, because wheter to update node’s version is decided elsewhere.
Updating nodes all together you risk to induce inconsistency into network.
So there is one solution: updater needs to update the node, and the node needs to update the updater, kinda lol.
But it doesn’t answer the question: why updater’s size is 42 megs?
This is what the updater doing - it compares the NodeID with the cursor on https://version.storj.io
If your node is not eligible to update, it will wait for the next check.
I’ve used script above many times, including node transfer.
And it works just great.
I have 8 nodes and updaters on single OC installed as services.
They work flawlessly.
Also I tested node transfer - it works without any drawbacks.
The only thing you should carry about is when you generate config only in setup_node.bat - you will have to manually adjust allocated and advertised sizes of the node. Since config is taken from script’s initial settings.
Why not Storj DCS?
You can easily create an account, upload a file and share it.
You can also limit time (until 2021-06-15 11:00:00 for example, or +2w)
