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

serverless-codepipeline

v1.0.3

Published

CI CD for serverless framework

Downloads

8

Readme

serverless-codepipeline

Add CI CD to your serverless application instantly

Getting Started

yarn add serverless-codepipeline

add plugin to the serverless.yml

plugins:
  modules:
    - serverless-codepipeline

Add following configuration in serverless.yml file

custom:
  cicd:
    branch: 'master'
    owner: '${REPOSITORY OWNER}'
    repository: '${REPOSITORY NAMW}'
    githubtoken: 'asdas'
    policy: '{
               "Version": "2012-10-17",
               "Statement": [
                 {
                   "Effect": "Allow",
                   "Action": [
                     "elasticbeanstalk:*"
                   ],
                   "Resource": "*"
                 }
               ]
             }'

Add buildspec.yml to folder, codebuild use buildspec.yml to deploy application most common example of buildspec.yml is

version: 0.1
phases:
  install:
    commands:
      - npm install
      - npm install -g serverless
  build:
    commands:
      - serverless deploy --stage prod

Some details on these parameters

Parameter | Info | Default | More Information ------ | ------ | ------ | ------ image (node) | If the runtime is nodeJS | aws/codebuild/nodejs:6.3.1 | Lookup other image identifiers image (python) | If the runtime is python | aws/codebuild/python:3.5.2 | Lookup other image identifiers image (other) | If the runtime is something else | aws/codebuild/ubuntu-base:14.04 | Lookup other image identifiers branch | The git branch CodePipeline monitors | master | More on how CodePipeline starts owner | The owner of the GitHub repository | blank | Required as no default repository | The GitHub repository CodePipeline monitors | The name of your service | More on how CodePipeline starts githubtoken | The GitHub OAuth token for private repos | blank | How to get a token excludestages | Stages you don't want CICD for | blank | Serverless stages


Contributing

Open an issue first to discuss potential changes/additions. If you have questions with the guide, feel free to leave them as issues in the repository. If you find a typo, create a pull request. The idea is to keep the content up to date and use github’s native feature to help tell the story with issues and PR’s, which are all searchable via google. Why? Because odds are if you have a question, someone else does too! You can learn more here at about how to contribute.

By contributing to this repository you are agreeing to make your content available subject to the license of this repository.

Process

1. Discuss the changes in a GitHub issue.
2. Open a Pull Request, reference the issue, and explain the change and why it adds value.
3. The Pull Request will be evaluated and either merged or declined.

License

Use this guide. Attributions are appreciated._

Copyright

Copyright (c) 2014-2015 Tushar Borole

(The MIT License)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Last but not least

This is made in San Francisco with love and passion ʕ´•ᴥ•`ʔ