swarm-cli
swarm-cli copied to clipboard
ethersphere
Manage your Bee node and interact with the Swarm network via the CLI
I can imagine having a `cid` command for converting between different reference representations and also for displaying detailed information about CID encoded references (example: https://cid.ipfs.io/#bah5acgzazxeiyx6fr4i6nhua4uvxtqczdupn5ehhmpv5ykl4vaezz6uxn4ya).
I've just uploaded 150 png images for a NFT series release and used the following script: ``` for f in *.png; do swarm-cli upload $f \ --stamp [...] \ --name...
It would be good to have a command to list all the versions of a feed. For example: ``` $ swarm-cli feed list 27fbef742c9a9c9ef82c67694784229c62c15d10bb9a161f8e0258e693f1d45b [... list of feed update references...]...
Sometimes it may take 30 seconds on my older computer to return to the shell after an error. For example if I try to upload a file that is too...
``` .swarmmetadata.json .swarmgatewaypreview.jpeg ``` Either strip or keep it with a flag
``` 10:46:16 swarm-cli 0 s status -q | head -n 1 | grep "^OK" OK - Bee API Connection node:events:368 throw er; // Unhandled 'error' event ^ Error: write EPIPE...
It would be nice if the CLI supported bzz.links. Since that is an experimental feature it could be optional to print it, but it could accept bzz.link style links wherever...
My typical workflow is to use either a local node or a remote gateway node. Generally I try similar commands on them and it is a bit cumbersome to always...
when uploading a batch that has already expired, the cli does not respect the fact that the batch is already expired. this is observed with `v1.5.0`. reproduce with: - buy...
Metadata
Owner
Metadata
Manage your Bee node and interact with the Swarm network via the CLI