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

everyconfig

v1.0.2

Published

Use the same yaml config files in every language

Downloads

550

Readme

everyconfig

Use the same .yaml config files in every programming language

usage

Set up your config files in a directory like this:

.
├── config
|   ├── default.yaml
|   ├── production.yaml
|   └── test.yaml
├── foo
|   ├── foo.js
|   └── blue.js
└── bar
    ├── something.py
    └── post.py

Then set CONFIG_ENV to one of the names of your yaml files, like so: CONFIG_ENV=production node app.js

The best part is that all of your configs inherit the default values from default.yaml.

default.yaml:

db:
  url: 'localhost'
  port: 27017

production.yaml:

db:
  url: 'some.internal.dns'

resulting config for CONFIG_ENV=production:

db:
  url: 'some.internal.dns'
  port: 27017

node.js

var config = require('everyconfig')('./config')
console.log(config.mongodb.url)

(note that you can use NODE_ENV instead of CONFIG_ENV with node.js if you want)

python

from everyconfig import everyconfig
config = everyconfig('./config')
print config.mongodb.url

ruby

require 'everyconfig'
config = Everyconfig.load('./config')
puts c['mongodb']['url']

bash

from https://gist.github.com/pkuczynski/8665367 (note that if you use four space indents, your variables will be separated by two underscores instead of one)

everyconfig <config dir> <variable prefix>
source $path_to_everyconfig/bash/everyconfig.sh

# you should use an absolute path for the directory that holds your config files
DIR=$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )

#           directory        prefix
everyconfig "$DIR"/../config CONFIG_
echo $CONFIG_mongodb_url

contact me

Send me a pr or an email 😀