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

secret-config

v1.1.0

Published

A Node.js module for managing a multi-environment encrypted config file.

Downloads

3

Readme

secret-config

A Node.js module for managing a multi-environment encrypted config file.

This module uses my other module, yael-autoencrypt, to read and write to an encrypted config file. You should read the README for that module first.

This module is a convenience wrapper. It basically just takes a YAML formatted file with entries grouped by environment, and returns the correct configuration based on the current NODE_ENV.

Installation

npm install secret-config

Example usage

// First use
secrets = require('secret-config')(
  password: process.env.ENCRYPTION_PASSPHRASE
  plaintext_file: 'secrets.yaml'
  encrypted_file: 'secrets.encrypted'
)

// Subsequent use in other files can use cached results
secrets = require('secret-config')();

// If you do not want to cache results, useful if loading a second file
secrets = require('secret-config')(
  cache: false,
  password: process.env.ENCRYPTION_PASSPHRASE2
  plaintext_file: 'other-secrets.yaml'
  encrypted_file: 'other-secrets.encrypted'
)

Config file

It can read YAML or JSON and returns a JavaScript object. What configuration it returns depends on process.env.NODE_ENV. Each environment gets its own top-level key. Settings common to all environments can be placed in the 'common' key. Any values in the environment keys will override or be added to the values in 'common'.

Example file:

common:
  session:
    secret: 'express session secret'
  auth:
    user: 'test'
    pass: 'test'
development:
  mongo:
    db_uri: 'mongodb://localhost:27017/users'
production:
  auth:
    user: 'admin'
    pass: 'very long secure password'
  mongo:
    db_uri: 'mongodb://user:[email protected]:27017/users'
  google_analytics:
    WebPropertyID: 'UA-12345678-9'

When run with NODE_ENV=development, secrets would equal:

{
  session: {
    secret: 'express session secret'
  },
  auth: {
    user: 'test',
    pass: 'test'
  },
  mongo: {
    db_uri: 'mongodb://localhost:27017/users'
  }
}

But when run with NODE_ENV=production, secrets would equal instead:

{
  session: {
    secret: 'express session secret'
  },
  auth: {
    user: 'admin',
    pass: 'very long secure password'
  },
  mongo: {
    db_uri: 'mongodb://user:[email protected]:27017/users'
  },
  google_analytics: {
    WebPropertyID: 'UA-12345678-9'
  }
}