idea: cyphernode control script

[darwin]

While writing my thoughts about #87 I got few ideas. Please let me share them here.

I would love to see a single more polished tool for managing cyphernode(s) on my host machine.

AFAIK current workflow is to call ./dist/setup.sh and then use ./dist/start.sh. Then user can rely on web interface https://localhost/welcome or inspect mapped data folders or interact directly with docker(-compose).

It would be nice to have one "umbrella" tool, say cn which I could put on path and control my cyphernode from it.

I think cyphernode configuration and installation should be conceptually two separate commands. User should be aware that he first does cn configure which asks questions and gives him a reproducible recipe file (your current config.sh or something like that) and then he calls cn build <config> to reproducibly build docker containers and prime his host machine (what you call INSTALL in setup.sh) to later cn start or cn stop.

While cyphernode is running he should be able to use other commands to inspect it or control it. E.g. he could access logs via cn logs ... or could access cli interfaces (like bitcoin-cli) from bitcoin container and other tools like that. In other words I'd like to see powerful wrapper tool to control cyphernode from host machine via cli. And IMO this should be the primary tool before you focus on building/exposing web interfaces. I'm not against them, but host machine cli tool must come first.

I just did something like this on much smaller scale in my other project. Please look at the source of the ./sv tool (in bash).

If you like the concept, I'd like to volunteer to build something along those lines for cyphernode (This assumes integrating current setup.sh, start.sh, stop.sh and maybe other control scripts I'm not yet aware of.)