npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

yayaml-config

v0.0.4

Published

Yaml configuration reader for multiple environments from a single settings file

Downloads

9

Readme

yayaml-config

Yet another yaml configuration module for Node.js. The settings can be defined with yaml for different environments (e.g. production and development) in a single file. Shared settings can be defined in the default environment. Choose the environment using NODE_ENV.

There are several similar modules on npm. This is based on yaml-config, but this uses a more idiomatic node style.

Installation

Clone the repo until this is put in npm registry.

Defining settings

The settings file can define one or more environments. default is used in all environments. Settings are merged for the environment that is defined.

default: 
  redis: 
    port: 6379
    host: 127.0.0.1
    db: 1
    options: {}
test: 
  redis: 
    db: 12
production: 
  redis: 
    host: 192.168.1.2
    db: 0

If the environment is set to test, redis.db is set to 12. If the environment is set to production, redis.db is set to 0. Otherwise, redis.db is set to 1.

Usage

To define the environment, set NODE_ENV on the command line, or set it in the code. If no environment is set development is assumed.

var config = require('yaml-config-reader')
  , configFile = './config-example.yaml';
config.read(configFile, function (err, settings) {
  if (err) { console.error(err); return err; }
  console.log('\nSettings for default (development)');
  console.log(util.inspect(settings));
});

The readConfig() function optionally takes a second parameter as enviroment name. If you do not define an environment, the development configuration will be loaded. For example:

config.read(configFile, 'test', function (err, settings) {
  if (err) { console.error(err); return err; }
  console.log(settings.redis.db);
});

The updateConfig() function will take current settings and save them back to the configuration file:

config.read(configFile, 'production', function (err, settings) {
  if (err) { console.error(err); return err; }
  console.log('\nCurrent settings for production');
  console.log(util.inspect(settings));

  settings.redis.host='192.168.1.2';
  config.update(settings, configFile, 'production', function (err, newSettings) {
    if (err) { console.error(err); return err; }
    console.log('\nUpdated configuration file:');
    console.log(newSettings);
  });
});

License

yayaml-config is freely distributable under the terms of the MIT License.

Copyright (c) UT-Battelle, LLC (the "Original Author")

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, THE U.S. GOVERNMENT, OR UT-BATTELLE 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.