accept network details, such as whether to use the testnet at startup

[thedavidmeister]

testnetify.sh seems rather fragile to me, is it really OK to rewrite files that npm manages in a way that it is not aware of?

e.g. what stops the modifications getting blown away the next time npm updates the byteballcore dependency?

is there any way that network details could be passed through at startup?

[tonyofbyteball]

e.g. what stops the modifications getting blown away the next time npm updates the byteballcore dependency?

This is what happens. I have to testnetify again after doing npm update on my testnet nodes. I risk to forget to do it, but it makes no damage other than the node staying offline.

Suggestions are welcome. I feel like conf.json is not the right place to define the network because conf defines the config of the node on the given network while testnet/livenet is about the network -- different levels of the hierarchy.

[tarmo888]

Running this cp .env.testnet .env will now switch to testnet
6662f61