Config and environment files

[JuanMartinP]

#14
Add config and .env files.

[fgalan]

Two comments:

• A config.md doc file should be included about configuration
• It is a common practise in our platform to plefix env vars with the name of the componente (e.g. ORION_ in the case of CB). In this case, I'd suggest to use FDA_ (except for NODE_ENV... not sure if we prefix it in other components, pls check)

[AlvaroVega]

I guess here we can and all env vars needed for postgresql, mongo, minio, aws (tipical endpoint and credentials) as well as fda would need (port, .. ).

[fgalan]

I guess here we can and all env vars needed for postgresql, mongo, minio, aws (tipical endpoint and credentials) as well as fda would need (port, .. ).

I agree

In general, all that now is hardwired in the code should be exposed in configuration.

[fgalan]

This file should be linked from main README.md (documentation section)

[JuanMartinP]

Added in commit f00af80

[fgalan]

Postgre, Postgres or PostgreSQL? Which one is the proper term?

(I tend to think it is PostgreSQL)

[JuanMartinP]

Well after research apparently postgre is the only one no one uses. I thought it was the correct abbreviation but Postgres was the original name of the product so its what's usually used. Changed to PostgreSQL in the commit 341e5f2.

[fgalan]

Maybe we should use

FDA_PG_...

?

as we did recently in Kafnurs (e.g. KAFNUS_TESTS_PG_USER)

[JuanMartinP]

Changed in commit 608ada7

[AlvaroVega]

LGTM and pass ball to @fgalan

[fgalan]

LGTM