If implemented, the user could run something like configya server/config.json and get a list of which environment variables would be needed to override keys in the config.
Proof of concept / working example: https://gist.github.com/9bbb9a1c38078788c511
Example command-line usage of that Gist
node ./configparse.js server/config.json --prefix LK
Input: config.json
{
"nested": {
"setting": {
"value": true
},
"other": [ "cool" ]
}
}
Output:
LK_NESTED_SETTING_VALUE="true"
LK_NESTED_OTHER="[\"cool\"]"
Thoughts?