Advice on Minimising the number of Environment Variables

We have seen environment variables being _miss-used_ to store _all_ configuration variables...
This creates issues when these variables are encrypted and stored on Travis-CI (_and thus no longer visible_) so when they need to be changed it's a chore.

A _better_ approach is to keep the _bare minimum_ "secret" values in environment variables and any non-sensitive configuration in the `package.json` or other `config.json` file.