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

genvv

v0.2.4

Published

Genearte .env files based on data sources

Downloads

27

Readme

genvv

This is a tool that helps creating environment files by collecting data from various apis (providers) as source for variables and values.

Installation

$ npm install -g genvv

Providers

The default providers for AWSare AWS Parameter Store and AWS Secrets Manager.

Right now genvv supports:

  • AWS Parameter Store
  • AWS Secrets Manager
  • Heroku (config vars)

Provider order is important, for example in [p1, p2], values from p1 will take precedence.

Usage

This is a quick example about it. Let's say we need to set a variable FOO=bar in our application environment:

AWS

Ensure the host from which your application is deployed has access to it through AWS credentials or IAM role, and it has the correct policies applied.

Parameter Store & Secrets Manager

Create a file with a list of environment variables to set during deploy. Example:

# All variables will get a value from a provider source.
# Comment lines are removed.
DATABASE_HOST # From Parameter Store
DATABASE_PASSWORD # From Parameter Store
DEFAULT_VARIABLE="default-value"
db/data-postgres # From Secrets Manager

Execute like:

genvv --aws --region=us-east-1 --env-vars my-env-vars-file > .env

It will then get the values for the variables and put the .env file in the host where our application runs.

Heroku

For Heroku we need the app name and the API token

Execute like:

genvv --heroku --heroku-token=[your-token]--heroku-app-name=[app-name] > .env

It will then get the values for the variables and put the .env file in the host where our application runs.

$ npm install -g genvv
$ genvv --version
v0.0.1
$ genvv --help
  Usage:
    genvv [OPTIONS] --env-vars [FILE]
  
  General options:
    --help                Print this help info and exit
    --version             Print version of this command and exit
  
  Runtime options:
    --aws                 Specifies we're gonna use AWS providers
    --heroku              Specifies we're gonna use Heroku providers

    AWS Options:
      --region            AWS region to use. E.g.: us-east-1
      --env-vars          Environment variables (file location) to look for in AWS providers
    
    Heroku Options:
      --heroku-token      API Token
      --heroku-app-name   App name from where we're getting the config variables
  
  Output options:
    --add-export     Add "export" before each ENV var
  
  See <https://github.com/mrtrom/genvv> for more complete docs
  Please report bugs to <https://github.com/mrtrom/genvv/issues>