A configuration scheme that might be easier to maintain over using .env files.

[peterMuriuki]

We have so far been using .env files to configure both this react application and the accompanying backend express service. This has so far worked nicely for simple env values. i.e envs whose values were primitive types and could be easily encoded into a string and later converted to their proper types in the code. However, using envs has become harder when working with more complex envs. envs like Sentry configs which take the form of json and could have nested levels. Its even harder and less maintanable to write deployment scripts for populating such envs.

I think a better solution would be something similar to config.js files. a config interface that is based on the underlying programming language, javascript in this case. This would make it easier to think about, modify and maintain deployment scripts. One such tool that we could potentialy use is

• https://blog.logrocket.com/creating-configuration-files-node-js-using-node-config/