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.
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.jsonor otherconfig.jsonfile.