nodejs/nodebestpractices
1
0
Fork 0
mirror of https://github.com/goldbergyoni/nodebestpractices.git synced 2025-11-01 18:46:54 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'master' of https://github.com/i0natan/nodebestpractices

Browse Source
This commit is contained in:
idori
2017-10-14 16:56:28 +03:00
parent 719ea6356c 11635d963b
commit b43dc8b0a8
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@ -87,11 +87,11 @@
## ![✔] 1.6 Use environment aware, secure and hirearchical config
**TL;DR:** Monitoring is a game of finding out issues before our customers do – obviously this should be assigned unprecedented importance. The market is overwhelmed with offers thus consider starting with defining the basic metrics you must follow (my sug
**TL;DR:** The perfect and flawless configuration setup must include (a) keys that can be read from file AND from environment variable (b) secrets are kept outside committed code (c) config is hierarchical for easier findability. There are only a few packages that can help tick all those boxes
**Otherwise:** You end-up with a blackbox that is hard to reason about, then you start re-writing all logging statements to add additional information
**Otherwise:** Failing to satisfy any of the config requirements will simply bog down the development or devpos team, or both
🔗 [**Read More: Structure by feature*](/sections/errorhandling/configguide.md)
🔗 [**Read More: configuration best practices*](/sections/projectstructre/configguide.md)
<br/><br/>
@ -585,4 +585,4 @@ Text here...
Text here...
<br/><br/>
<br/><br/>