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

envgate

v0.0.9

Published

reads in and replaces the keys in the task definition from the .envgate file

Downloads

6

Readme

ENVGATE (ENV for Fargate)

Simple tool which allows to replace fields within a file with the interpolate syntax.

{
    "NAME": "Erik",
    "STATEMENT": "Hello ${NAME}!"
}

Will become

{
    "NAME": "Erik",
    "STATEMENT": "Hello Erik!"
}

Why?

This project was made for Fargate but can really be used anywhere. It allows you to easily replace and update env varibles with ease.

If you wish to insert values based on you env in you fargate you can use the command

envgate --target task-definition.json --fields .aws-config.json --env STAGE production

{
"executionRoleArn": "arn:aws:iam::${AWS_PROFILE}:role/${ROLE_NAME}-$STAGE",
"name": "${FARGATE_NAME}",
"ulimits": [],
"dnsServers": [],
"mountPoints": [],
"dockerSecurityOptions": [],
"volumesFrom": [],
"image": "${IMAGE_NAME}"
}

Commands

-t, --target [string] (required) Path for the target file. This file is where the fields will be replaced. It will filter out any fields that are not within this json.

-o, --output [string] Path for the outputted file

-f, --fields <string...> Path for the fields files which should be able to replace. You can include more files than you target to easy be able to edit the fields you wish to replace. You can add more than one fields files per command. You can have a structure like this.

/config.json/config.prod.json/config.staging.json/target.json

When building for a staging environment

envgate -f config.json -f config.staging.json -t target.json

And when building for a prod environment

envgate -f config.json -f config.prod.json -t target.json

-e, --env <string...> Extra enviroment varibles. You can add extra varibles which are part of the replace protocol. Should be use in the following way

envgate -e <KEY> <VALUE> --target target.json

If you have a specific stage or similiair it can be easy to just add the stage as a seperate varible.

envgate -f config.json -e STAGE prod -t target.json

-g, --get [string] Get a certain value in the env instead of building the output file

-pe, --process-env Uses the env varibles within the project aswell