swarm-cli
swarm-cli copied to clipboard
Manage your Bee node and interact with the Swarm network via the CLI
simply `tx:0x...` would mean a lot to the user, i think. it is expected web3 ux. otherwise it is not obvious what is going on.
It's possible to build a single binary executable without dependencies and it may make it easier to distribute the CLI to users who don't have Node and NPM installed. There...
It would be good if it were possible to use ENS domains wherever it's possible to use a reference. For example: `swarm-cli manifest list example.eth`
Provide cli utility for https://docs.ethswarm.org/api/#tag/Stewardship
``` root@sig-bee-main-02:~/bee# swarm-cli feed print -v --stamp 2c6ea071030ea672a5502472b0acdb70aafa18cb7eda1bf142b2948241122153 -i main Looking up feed topic 0000000000000000000000000000000000000000000000000000000000000000... Chunk Reference: d755aa1e5b2e059f7013dbdd6e1134fbc00976c5254c176a74ef24f1ce60f06f Chunk Reference URL: http://localhost:1633/bzz/d755aa1e5b2e059f7013dbdd6e1134fbc00976c5254c176a74ef24f1ce60f06f/ Feed Index: 0000000000000005 Next Index: 0000000000000006 Feed Manifest:...
eg. ``` swarm-cli configure bee-api-url http://api.gateway.ethswarm.org ```
As described for example here: https://fishshell.com/docs/current/completions.html#where-to-put-completions the user-land completions should be put into `~/.config/fish/completions/` and not into `config.fish` file.