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

serfdom

v1.0.7

Published

Deploys AWS Elastic Beanstalk applications

Downloads

9

Readme

Serfdom

The easiest way to create identifiable environments for Elastic Beanstalk applications.

Run serfdom and create the master-2-2-1-6a8ea5e environment.

Serfdome will ask for the NODE_ENV variable to use (development, staging or production by default), and create a new EB environment for your application with a unique name of <branch name>-<application version>-<git commit sha> for you to easily be able to identify your environments.

Why

This is the perfect module to use if you want zero downtime deployments using CNAME swaps in AWS Elastic Beanstalk.

Our suggestion is to tie a DNS record to a specific application CNAME. For example, manually create your first EB environment named my-app-prod.elasticbeanstalk.com. Then, through your DNS records, map my-app.com to CNAME my-app-prod.elasticbeanstalk.com.

From that point forward, use this serfdom app to launch new environments. They will be specifically identifiable to what code is contained in the environment. Then, when you are happy with an environment, do a Swap CNAMEs through Elastic Beanstalk to switch your prod CNAME with your newest environment. You then have a non-destructive rollout plan for production releases.

Prerequisites

  • Your application must already be an AWS Elastic Beanstalk application.

You can do this by installing the AWS CLI and running eb init in your applications root directory

How to Install

npm i -g serfdom

How to Use

  1. cd my-eb-app
  2. serfdom
  3. ...
  4. profit!

Configuration

Serfdom can run in any Elastic Beanstalk application out of the box. But you can also specify a .serfdom JSON configuration file with the following parameters.

Environment Type List

You may specify an array of strings to use as your environment names. This will specify both the NODE_ENV environment variable, and it will be included in the environment name/url.

Example .serfdom configuration override:

"environments": [
  "red",
  "blue"
]

Environment Tags

An array of strings to add as tags to your AWS environment. serfdom will always add the tag environment=${CHOSEN_ENV_TYPE}

AWS imposes the following restrictions on tags:

  • Keys and values can contain any alphabetic character in any language, any numeric character, white space, invisible separator, and the following symbols: _ . : / + - @
  • Keys can contain up to 128 characters. Values can contain up to 256 characters.
  • Keys and values are case sensitive.
  • Values cannot match the environment name.
  • Values cannot include either aws: or elasticbeanstalk:.

Example .serfdom configuration addition:

{
  "tags": [
    "project=example",
    "team=extreme"
  ]
}