Node migration option to provide own seed

[tmchow]

Feature request:

Param to take in an existing seed for those people that are setting up new node and need to use an existing seed. I've setup my node like a dozen times in the last 6 months for a variety of reasons, so this would save me some time. I'm sure others have this need as well.

[lephleg]

@tmchow thanks for the suggestion. I've also thought of it a while ago. It's definitely something I'd use a lot too.

However, the reason I didn't include it as part of the installer was the security concerns it may raise to some people. Asking for a wallet seed as part of an automated sudo script may ring some bells (it would to me). Especially user with no clear overview of how the whole stack operates could criticize it and not spare a minute to check the actual code.

On the other hand, I may implement it and mark it with a bold note for those that may want to use it after they've dig in more. Haven't decide yet.

[tmchow]

@lephleg Good point. Perhaps a good middle ground is:

1. add flag for migration but don't take seed as a param
2. instead just output a message at the every end on what syntax the user should do to change the seed

[lephleg]

Nano node v.18 brings a new option on the --wallet_create CLI command which allows a new wallet to be imported using a provided seed:

$ docker exec -it nano-node --wallet_create --key=<seed>

This could make things way easier for the installer too. I'll give it a go on first chance.