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

codeship-restart-lambda

v1.0.5

Published

Restart the last build of a Codeship project using Lambda

Downloads

17

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

trolleymusictrolleymusic

Keywords

Readme

codeship-restart-lambda

Restart the last build of a Codeship project using Lambda - 1.0.0 now only works with Codeship API version 2 - use version 0.1.0 for version 1

Installation:

  • Run npm install
  • Run npm run setup, this creates a number of config files
  • Edit .env to contain your AWS settings like credentials, AWS region etc
  • Edit .deploy.env to contain:
    • ~~CODESHIP_API_KEY - required, your Codeship API v1 key~~
    • CODESHIP_USERNAME - required, your Codeship user's username
    • CODESHIP_PASSWORD - required, your Codeship user's password
    • CODESHIP_ORG_NAME - required, your Codeship organisation name -- either this and/or CODESHIP_ORG_UUID are required
    • CODESHIP_ORG_UUID - required, your Codeship organisation uuid -- either this and/or CODESHIP_ORG_NAME are required
    • CODESHIP_REPOSITORY_NAME - required, your Codeship's project repository name
    • CODESHIP_BRANCH_NAME - optional, a branch name to filter - defaults to master - you can also set this to '*' to restart the last build of every branch
    • CODESHIP_TESTING - optional, when true aborts the application before telling Codeship to restart the build thereby saving on build counts
    • CODESHIP_INCLUDE_TAGS - optional, when true and CODESHIP_BRANCH_NAME is set to * it will include all tags, which build as separate branches in Codeship, otherwise it ignores them
  • Run npm run package to build and pack a zip to upload to Lambda
  • Upload the zip to Lambda
  • Set the environmental variables again in Lambda

TODO:

  • Currently npm run deploy isn't working. It seems to be but then the function never shows up in Lambda - get this working so I don't have to upload anything