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

env-cobbler

v1.0.0

Published

Cobbler

Downloads

4

Readme

Cobbler

Configuration

From a development environment

Set the AWS credentials in ~/.aws/credentials file:

[default]
aws_access_key_id = <AWS_ACCESS_KEY_ID>
aws_secret_access_key = <AWS_SECRET_ACCESS_KEY>

Specified key must have a permission to read secrets from the AWS Secrets Manager.

It is not possible to resolve references via the EC2 Loopback interface if not running from inside an EC2 instance.

From inside an EC2 instance

Permissions must be configured by assigning roles with the appropriate policies to an EC2 instance.

Environment variables

AWS Secrets Manager

Set environment variables to ARN urls of their actual values prepended with the cobbler protocol:

process.env.EVERYTHING = 'cobbler://arn:aws:secretsmanager:eu-west-1:123456789123:secret:TheAnswerToUniverseAndEverything-0Z6hib'

If secret stored contains JSON value, you can use the pipe character to extract the necessary JSON property.

process.env.POSTGRES_HOST = 'cobbler://arn:aws:secretsmanager:eu-west-1:123456789123:secret:PostgresRDS-E8dwh4|host'
process.env.POSTGRES_PORT = 'cobbler://arn:aws:secretsmanager:eu-west-1:123456789123:secret:PostgresRDS-E8dwh4|port'

EC2 Loopback Interface

process.env.HOSTNAME = 'cobbler://ec2:loopback:/latest/meta-data/hostname'

Running application

Run application from the package root with:

npx cobbler

Environment variable references will be resolved and the npm start script executed from the same directory.