[feature request] adex-cli

[ca333]

could use a mm2-cli with intuitive user interface, full adex functionality coverage and noob-proof mm2 initialisation / "process-manager". e.g. ./adex-cli start (should do all the magic and only ask whats absolutely required & inform user ref storage location of encrypted seed-file, ...), ./adex-cli getbalance KMD , ./adex-cli send RHJ9Ym1dJcS2uTj3jfmLkg43JcZMhQqpLi 3.33 KMD, ./adex-cli stop, et cetera

Roadmap:

• [v0.1.0] basic adex req-rep client
• [v0.1.1] adex-cli mm2 process init & manager
• [v0.2.0] command line GUI ("QA mm2 debug tool")

v0.3.0 TBA

[borngraced]

Good idea,
I have a note, adex-cli start should just be adex no need to explicitly include cli making the commands simpler to use e.g adex start, adex getbalance KMD @ca333

[rozhkovdmitrii]

Guys, @ca333, @borngraced, just to let you know.

I have the following plan for the version 0.1.0. I would predefine four scenarios:

1. init-mm-cfg
2. init-coins
3. start
4. stop

init-mm-cfg

To create a new or rewrite an existent mm configuration at first. It's important to note I would let QA engineer to fill configuration using questionnaire with predefined default values.

Initialize mm2 configuration in the questionnaire mode

Usage: adex init-mm2-cfg [OPTIONS]

Options:
      --cfg-file <CFG_FILE>  file path to save mm2 configuration [default: MM2.json]
  -h, --help                 Print help

init-coins

To set up on of predefined set: empty, rick-morty, full. Selected set will be downloaded or just created.

Initialize predefined mm2 coin set

Usage: adex init-coins --coin-set <COIN_SET>

Options:
      --coin-set <COIN_SET>  to select out of predefined sets [possible values: empty, rick-morty, full]
  -h, --help                 Print help

start

Start mm with a default or custom configuration

stop

Stop mm as a service and/or using stop request )

---

That is it for the version 0.1.0, further I will grow commands with the available set (get-balance, send etc.)

[ca333]

Guys, @ca333, @borngraced, just to let you know.

I have the following plan for the version 0.1.0. I would predefine four scenarios:

1. init-mm-cfg
2. init-coins
3. start
4. stop

init-mm-cfg

To create a new or rewrite an existent mm configuration at first. It's important to note I would let QA engineer to fill configuration using questionnaire with predefined default values.

Initialize mm2 configuration in the questionnaire mode

Usage: adex init-mm2-cfg [OPTIONS]

Options:
      --cfg-file <CFG_FILE>  file path to save mm2 configuration [default: MM2.json]
  -h, --help                 Print help

init-coins

To set up on of predefined set: empty, rick-morty, full. Selected set will be downloaded or just created.

Initialize predefined mm2 coin set

Usage: adex init-coins --coin-set <COIN_SET>

Options:
      --coin-set <COIN_SET>  to select out of predefined sets [possible values: empty, rick-morty, full]
  -h, --help                 Print help

start

Start mm with a default or custom configuration

stop

Stop mm as a service and/or using stop request )

That is it for the version 0.1.0, further I will grow commands with the available set (get-balance, send etc.)

sounds good - from a UX perspective we could probably even combine 1. and 2. for sake of simplicity into a general init.