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

ecsdeploy

v2.0.5

Published

A tool to help you deploy AWS ECS Services

Downloads

30

Readme

ECS Deploy

CircleCI

A very simple tool to update tasks Amazon ECS services

npm install -g ecsdeploy

Use as a CLI tool

Let's say we have a task definition file for an ECS service:

{
  "family": "myTestTaskDef",
  "containerDefinitions": [
    {
      "memoryReservation": "300",
      "essential": true,
      "name": "myContainer",
      "image": "myApp:latest",
      "cpu": "300"
    }
  ]
}

ecsdeploy makes it really easy to deploy.

ecsdeploy -s myService -c myCluster -t myTaskDef.json

{ taskDefinition: 'arn:aws:ecs:eu-west-1:12345678909:task-definition/myTestTaskDef:26',
service: 'arn:aws:ecs:eu-west-1:12345678909:service/myService',
cluster: 'arn:aws:ecs:eu-west-1:12345678909:cluster/myCluster' }

It's also possible to pipe the task definition JSON into ecsdeploy.

cat taskDef.json | ecsdeploy -s myService -c myCluster

{ taskDefinition: 'arn:aws:ecs:eu-west-1:12345678909:task-definition/myTestTaskDef:26',
  service: 'arn:aws:ecs:eu-west-1:12345678909:service/myService',
  cluster: 'arn:aws:ecs:eu-west-1:12345678909:cluster/myCluster' }

Use Programmatically

const ecsDeploy = require('ecsdeploy')

var opts = {
  taskDefinition: require('./taskDef.json'),
  service: 'myService',
  cluster: 'myCluster'
}

ecsDeploy(opts, (err, result) => {
  console.log(result)
})

Why is ecsdeploy needed?

I found that many of the hosted build servers (CircleCI, TravisCI, etc.) do not have plugins for ECS deployments.

I wanted a simple solution that could be used on any build server Let's say we have a CI/CD pipeline that deploys services to AWS ECS. We generally render the task definition JSON during the build process because every build has different outputs such as image tags, environment variables etc.

By passing the rendered JSON into ecsdeploy, it becomes incredibly simple to kick off deployments in ECS, regardless of the build system you use.