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

github-webhook-deployer

v1.0.0

Published

Deploys changes using github push events.

Downloads

11

Readme

github-webhook-deployer

deploys changes using github push events.

var deployer = require('github-webhook-deployer');

var server   = http.createServer(deployer({
    path : '/webhook',
    secret : 'testSecret' 
})).listen(3000);

Operation

  1. When a push event occurs, the current directory's branch is compared to the push event branch.
  2. If they are the same, git pull; npm install and then terminate the server process.
  3. The server process is restarted by foreverjs (or an equivelent daemon manager).
  4. Deployment is complete and you are running the latest code.

Example

Somewhere in the cloud there are two copies of a server, production and development. The production branch is in ~/production and the development is in ~/development. Both servers are started using the daemon manager foreverjs.

Now a developer wants to make some changes to the code. The developer does a checkout of the development branch on their local laptop/workstation, they run the server locally and make some changes. The developer can then push the changes to github.

Github webhooks broadcast the developer's change event to the production and development servers in the cloud. The development server sees the update, pulls in the changes and restarts. The developer can now test the changes on development server in the cloud.

Once satisfied the development server is stable, he/she can merge the changes into the production branch. Another push event is triggerd and this time the production server sees the update, pulls in the changes and restarts. No SSHing into the server, git pulling, and restarting the server. All is well.

Tutorial

Deploying to your server with a git push using Github webhooks and Forever.js