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

aws-buddy

v1.0.11

Published

AWS Buddy: A Build Manager backed by an S3 bucket

Downloads

7

Readme

AWS Buddy: A Build Manager backed by an S3 bucket

What's AWS Buddy?

AWS Buddy is a command line tool that helps you use an S3 bucket as a simple build manager.

Usage

# install it (globally)
$ npm install aws-buddy -g

# use it (generates default config on first use)
$ buddy --help

# config it (you'll need to make some edits before this will work for you)
$ vi ~/.aws-buddy.json

Typical Workflow and S3 Directory Structure

build
    archive
    env
        dev
        stage
        prod
  1. buddy push download remote build and upload it to dev.
  2. buddy info display the status of all environments.
  3. buddy promote --env dev copy build from dev to stage.
  4. buddy promote --env stage --ver 1.2.0 copy build from stage to prod and put a versioned copy in the archive directory.

It's just a file mover! But the thought is that you can setup your deployments to pull from the corresponding environment directory.

Commands

  • push : download remote build & upload to first environment (dev)
  • push-local : upload local build to first environment (dev)
  • promote : copies specified env build to configured promotesTo env. may also archive based on configuration. --env is required, --ver may be required. example: buddy promote --env stage --ver 1.16.1
  • info : list the current status of each environment
  • bucket : list the contents of the configured bucket

Config

After first run a config file will be generated into your home dir.

~/.aws-buddy.json

Note: You can specify a different config file by using the -f, --file options. This is useful if you want to use AWS Buddy with multiple different applications.

You will need to edit this file. Here is an example...

    {
        "awsRegion": "us-east-1",  // AWS S3 region
        "awsProfile": "user2"  // AWS Named Profile for alternate credentials - OPTIONAL (you will normally not need this)
        "bucket": "S3_BUCKET_NAME", // AWS S3 bucket name
        "buildFileName": "MyCoolAppBuild.zip", // build file name in S3
        "localBuildFile": "~/dev/MyCoolAppBuild.zip", // location of the local build file, used in the push-local cmd
        "infoFile": "info.json", // name of the meta file that is written to S3
        "archive": {
            "dir": "build/archive", // archive s3 dir
            "prefix": "MyCoolApp-", // archive file name prefix
            "suffix": ".zip"  // archive file name suffix
        },
        "remoteBuild": {
            "url": "http://buildserver.net/MyCoolAppBuild.zip", // url to download remote build, used in push cmd
            "user": "[email protected]",  // basic auth user
            "pass": "password-in-clear-fail",  // basic auth pass
            "localBuildFile": "~/temp/MyCoolAppBuild.zip" // location on local machine to save the downloaded build
        },
        // You can add additional environments or edit these.
        "environments": {
            "prod": {
                "label": "Production", // Display name
                "key": "prod", // must match hash key
                "order": 3,  // order lower goes first
                "dir": "build/env/prod",  // dir in s3
                "promotesTo": false,   // where does this env promote to
                "archiveOnPromote": true  // should we archive when an env is promoted to this env
            },
            "stage": {
                "label": "Stage",
                "key": "stage",
                "order": 2,
                "dir": "build/env/stage",
                "promotesTo": "prod",
                "archiveOnPromote": false
            },
            "dev": {
                "label": "Development",
                "key": "dev",
                "order": 1,
                "dir": "build/env/dev",
                "promotesTo": "stage",
                "archiveOnPromote": false
            }
        }
    }

NPM