accept passphrase, etc. as environment variables to facilitate easier devops

[thedavidmeister]

ideally i'd like to be able to spin up an environment with ansible or something and have everything ready to go without manually logging in via ssh to (re)boot key processes periodically

also, being able to keep everything the same but swap between setups for testing (e.g. CI) would be handy

it's pretty common for vendors such as heroku, circle CI, travis, etc. to offer environment variables for this purpose

AFAIK environment variables don't come with any more/less security concerns than the current setup, but could make things much easier to manage

[thedavidmeister]

i got something basic working in my dev VM with a combination of expect and systemd in case anyone else is interested

[tarmo888]

I used empty passphrase and these worked for me: echo -n '' | node start.js - powershell echo -ne '\n' | node start.js - unix shell

[frank-bee]

I use an AWS codepipeline to deploy and launch a chat bot. This is what I had to do to properly complete the pipeline: 'nohup echo -ne 't\n' | node start.js > /dev/null 2>&1 &'

[tarmo888]

There is no longer need to use special commands for wallets that are not encrypted with passphrase. If you used empty passphrase or wish not to have passphrase then now you can add true value to bNoPassphrase configuration variable.

[frank-bee]

Environmental variable would still be required if passphrase is configured - which makes sense. E. G. for a docker / k8s setup which would be a great way to go for...