Creating the config.json before starting the daemon it's still a solid solution for the moment being.
That being said, most of the time the daemon operator would not want to craft manually a JSON (eg. dockerized deployments) to change some parameters like network, explorer, and fee.
So it would be very useful to add at least those as command-line arguments for the binary, that, if passed, would NOT overwrite the current configuration file if already exists (we have market for some network with some specific fee).
Creating the
config.jsonbefore starting the daemon it's still a solid solution for the moment being. That being said, most of the time the daemon operator would not want to craft manually a JSON (eg. dockerized deployments) to change some parameters like network, explorer, and fee.So it would be very useful to add at least those as command-line arguments for the binary, that, if passed, would NOT overwrite the current configuration file if already exists (we have market for some network with some specific fee).