Installations

npm install two-phase-live-config

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

8.9.3

NPM Version

5.5.1 Score

64.1

Supply Chain

70.4

Quality

70.8

Maintenance

50

Vulnerability

97.3

License

Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Contributors

1

Unable to fetch Contributors

View All 1 Contributors

Languages

1

JavaScript

JavaScript (100%)

Love this project? Help keep it running — sponsor us today! 🚀

Developer

stierma1

Download Statistics

Total Downloads

560

Last Day

2

Last Week

4

Last Month

15

Last Year

52

GitHub Statistics

MIT License

3 Commits

2 Watchers

1 Branches

1 Contributors

Updated on Apr 04, 2018

Maintainers

1

Package Meta Information

Latest Version

1.0.0

Package Id

two-phase-live-config@1.0.0

Unpacked Size

5.45 kB

Size

2.26 kB

File Count

4

NPM Version

5.5.1

Node Version

8.9.3

Total Downloads

Cumulative downloads

Total Downloads

560

Last Day

0%

2

Compared to previous day

Last Week

300%

4

Compared to previous week

Last Month

275%

15

Compared to previous month

Last Year

-14.8%

52

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

1

lively-config

two-phase-live-config

Usage Example

1//Terminal
2LIVELY_RESOLVERS="SECRET,HTTP,FILE,ENV" FILE="file:///Users/user/code/configs/config.json" HTTP="http://example.com" HTTP_INTERVAL=5000 SECRET="object://{\"foo\":\"bar\"}" ENV="env://" node index.js
3
4//In code
5var config = require("two-phase-live-config");
6config.ready.then(() => {
7  //config is ready
8  //See LivelyConfig library for api
9})

Description

This library is to support config setup via command line rather than application level setup.

To Library will check environment variables first for a 'LIVELY_RESOLVERS' environment variable whose format is a comma separated list of Environment Variable Names, these names will be used to resolve the underlying config values

The order of resolvers in the LIVELY_RESOLVERS determines the priority of resolution

Resolvers

File

1{ENV_NAME}="file://{absolute_file_path}"
2{ENV_NAME}_INTERVAL={NUMBER} (optional)

Object

1{ENV_NAME}="object://{JSON_STRING}"
2{ENV_NAME}_INTERVAL={NUMBER} (optional)

Environment Variable

1{ENV_NAME}="env://"
2{ENV_NAME}_INTERVAL={NUMBER} (optional)

HTTP or HTTPS

1{ENV_NAME}="http://{url}"
2{ENV_NAME}_INTERVAL={NUMBER} (optional)
3{ENV_NAME}_HEADERS={JSON_STRING} (optional)

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

SAST

Determines if the project uses static code analysis.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

1.7

/10

Last Scanned on 2025-02-10

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More