Alexey
January 7, 2026, 8:22am
6
It’s absolutely the same for any platform:
Testfocus
We published the first binaries for the multinode dashboard on Github Release v1.34.3 · storj/storj · GitHub . Please test them and let us know if you have any issues. The main objective of this test is to find out if the binaries are working on different operating systems and setups. If you are able to add a storage node and can see it on the multinode dashboard I would call that success. We can also start to look for some wrong numbers on any of the pages. For example, the payout pag…
You may also use a docker version, but I doubt that you want it
Perhaps a useful hack for you would be to export connection parameters for every node to the json files, then form an json array to import them at once.
storagenode info --config-dir <insert your storage node config dir here>
But redirect to the file:
storagenode info --config-dir <insert your storage node config dir here> --json > node1.json
Then add them all to the array:
jq '.' -s node1.json node2.json node3.json > nodes.json
now you should be able to import them:
multinode add nodes.json
Or using some bash:
for n in node{1..10}.json; do
multinode add $n
done
The format:
Yes, some kind of. Seems I just do not understand your question. Almost all data can be represented as a json, so the meaning of comparison with tables eludes me.
The actual format for info --json is
{
"id": "xxx",
"apiSecret": "yyy",
"publicAddress": "zzz:28967",
"name": ""
}
So the array of such objects will looks like
[
{
"id": "xxx",
"apiSecret": "yyy",
"publicAddress": "zzz:28967",
"name": ""
},
{
"id": "xxx2",
"apiSecret": "yyy2",
"…