sthope/gitea_templates
Template
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fix typo ()

Browse Source
This commit is contained in:
Tim Pap 2017-07-10 12:21:38 +03:00 committed by Vahid Panjganj
parent d71b614104
commit a4b1834fab
1 changed files with 1 additions and 1 deletions

2
README.md

@ -142,7 +142,7 @@ that's useful for a code reviewer. if you can link to an associated Jira ticket,
* Depending on project size, define separate `development`, `test` and `production` environments.
_why:_
> Different data, tokens, APIs, ports etc... may be needed on different environmenyts. You may want an isolated `development` mode that calls fake API which returns predictable data, making both automated and manually testing much easier. Or you may want to enbale google analytics only on `production` and so on. [read more...](https://stackoverflow.com/questions/8332333/node-js-setting-up-environment-specific-configs-to-be-used-with-everyauth)
> Different data, tokens, APIs, ports etc... may be needed on different environments. You may want an isolated `development` mode that calls fake API which returns predictable data, making both automated and manually testing much easier. Or you may want to enbale google analytics only on `production` and so on. [read more...](https://stackoverflow.com/questions/8332333/node-js-setting-up-environment-specific-configs-to-be-used-with-everyauth)
* Load your deployment specific configurations from environment variables and never add them to the codebase as constants, [look at this sample](./config.sample.js).