Initial commit

Author: roquie

.editorconfig

@@ -0,0 +1,13 @@
+#root = true
+
+[*]
+indent_style = space
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+max_line_length = 100
+indent_size = 2
+
+[*.md]
+trim_trailing_whitespace = false

.gitignore

@@ -0,0 +1,11 @@
+node_modules
+coverage
+.nyc_output
+.DS_Store
+*.log
+.vscode
+.idea
+compiled
+.awcache
+.rpt2_cache
+docs

.travis.yml

@@ -0,0 +1,18 @@
+language: node_js
+cache:
+  directories:
+    - ~/.npm
+notifications:
+  email: false
+node_js:
+  - '10'
+  - '11'
+  - '8'
+  - '6'
+script:
+  - npm run test:prod && npm run build
+after_success:
+  - npm run travis-deploy-once "npm run report-coverage"
+branches:
+  except:
+    - /^v\d+\.\d+\.\d+$/

README.md

@@ -0,0 +1,109 @@
+Javascript microservice configuration module
+--------------------------------------------
+
+Configuration module for microservices written on TypeScript. Specially created
+for follow up corporate standards of application configuration.
+
+## Installation
+
+```bash
+npm install --save configuration-js
+
+yarn add configuration-js
+```
+
+## Usage
+
+By default path to configuration directory and application stage
+loading from `/app/configuration` with `local` stage.
+
+1) Simple
+```ts
+import Configuration from 'configuration-js';
+
+const conf = new Configuration();
+conf.load();
+
+console.log(conf.all()); // get all config
+console.log(conf.get('foo.bar')); // get nested key use dot notation
+```
+
+2) If u would like override default values, you can pass 2 arguments to
+class constructor or set up use setters.
+
+```php
+import Configuration from 'configuration-js';
+
+const conf = new Configuration('./configuration', 'test');
+conf.load();
+
+conf.get('foo'); // full example on the top
+```
+
+3) If the operating system has an env variables `CONFIG_PATH` and `STAGE`,
+then values for the package will be taken from there.
+
+```bash
+export CONFIG_PATH=/configuration
+export STAGE=prod
+```
+
+```php
+import Configuration from 'configuration-js';
+
+const conf = new Configuration('./configuration', 'test');
+conf.load(); // loaded files from /configuration for prod stage.
+
+conf.get('foo'); // full example on the top
+```
+
+4) If u want to see logs and see how load process working,
+pass you logger to property:
+
+First, install logger (winston supported bu default):
+```bash
+npm install --save winston
+
+yarn add winston
+```
+
+Second, pass you logger to property like this:
+```ts
+import Configuration from 'configuration-js';
+import WinstonConsoleLogger from 'configuration-js/winston-console-logger';
+
+const conf = new Configuration();
+conf.logger = new WinstonConsoleLogger(winston.createLogger({
+  transports: [new winston.transports.Console()]
+}));
+
+conf.load();
+
+conf.get('foo'); // full example on the top
+```
+
+Also, your can pass any logger who implements library `LoggerInterface`.
+
+## License
+
+The MIT License
+
+Copyright © 2019 teamc.io, Inc. https://teamc.io
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

code-of-conduct.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/