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

@cumulus-test/deployment

v1.0.2-beta.0

Published

Deployment templates for cumulus

Downloads

9

Readme

Cumulus Deployment

This module includes cloudformation templates needed for a successful deployment of a Cumulus Instance. The templates can be used with kes, a node CLI helper for AWS CloudFormation.

Usage

  1. Copy app.example to a new deployment project.

  2. Edit app.example/config.yml and your deployment information

  3. Rename app.example to app.

  4. Execute kes command:

    $ ./node_modules/.bin/kes cf deploy --kes-folder app --deployment <my-deployment> --template ../cumulus/packages/deployment/app

config.yml Explained

| field | default | description | ----- | ----------- | ----------- | stackName | (required) | the name used as a prefix in all aws resources | stackNameNoDash | (required) | stackName with no dash | urs_url | uat.urs | urs url used for OAuth | api_backend_url | apigateway backend url | the API backend url | api_distribution_url | apigateway dist url | the API url used for file distribution | shared_data_bucket | cumulus-data-shared | the bucket has the shared data artifacts | buckets.internal | (required) | the bucket used for storing deployment artifacts | buckets.private | (required) | the bucket used for storing private ingest data | buckets.protected | (required) | the bucket used for storing protected ingest data | buckets.public | (required) | the bucket used for storing public ingest data | cmr.username | devseed | the username used for posting metadata to CMR | cmr.provider | CUMULUS | the provider used for posting metadata to CMR | cmr.clientId | CUMULUS | the clientId used to authenticate with the CMR | cmr.password | (required) | the password used to authenticate with the CMR | vpc.vpcId | (required if ecs is used) | the vpcId used with the deployment | vpc.subnets | (required) | the subnets used | defaults_users | cumulus core | list of default users included in all deployments | ecs.amiid | ami-9eb4b1e5 | amiid of an optimized ecs instance (differnet for each region) | ecs.instanceType | (required) | the instance type of the ec2 machine used for running ecs tasks | ecs.volumeSize | 50 | the storage on ec2 instance running the ecs tasks | ecs.availabilityZone | us-east-1a | the availibity zone used for launching ec2 machines | ecs.maxInstances | 1 | max number of ec2 instances to launch in an autoscaling group | ecs.desiredInstances | 0 | desired number of ec2 instances needed in an autoscaling group | es.name | es5 | name of the elasticsearch cluster | es.elasticSearchMapping | 4 | version number of the elasticsearch mapping used | es.version | 5.3 | elasticsearch software version | es.instanceCount | 1 | number of elasticsearch nodes | es.instanceType | t2.small.elasticsearch | size of the ec2 instance used for the elasticsearch | es.volumeSize | 35 | the storage used in each elasticsearch node | sns.<name> | N/A | name of the sns topic | sns.<name>.subscriptions.lambda.endpoint | sns2elasticsearch | lambda function triggered for each message in the topic | apis.<name> | N/A | name of the apigateway application | apiStage | dev | stage name used for each api gateway deployment stage | dynamos.<name> | N/A | name of the dynamoDB table | dynamos.<name>.read | 5 | number of reads per second | dynamos.<name>.write | 1 | number of writes per second | dynamos.<name>.attributes | N/A | list of attributes | sqs.<name> | N/A | name of the queue | sqs.<name>.visibilityTimeout | 20 | # of seconds the message returns to the queue after it is read by a consumer | sqs.<name>.retry | 30 | number of time the message is returned to the queue before being discarded | sqs.<name>.consumer | N/A | list of lambda function queue consumers | rules.<name> | N/A | list of cloudwathch rules | rules.<name>.schedule | N/A | rule's schedule | rules.<name>.state | ENABLED | state of the rule | rules.<name>.targets | N/A | list of lambda functions to be invoked | stepFunctions | N/A | list of step functions | lambdas | N/A | list of lambda functions