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

gulp-git-webhook

v0.1.0-alpha

Published

A Git(hub) webhook callback server to fetch new code (poor man CI)

Downloads

3

Readme

gulp-git-webhook NPM version Build Status Dependency Status

A Git(hub) webhook callback server to fetch new code (poor man CI)

This little tool is born out of real projects. Keep having to deploy and setup demo site etc. Why bother if you own the git account? You just need a new cert from github, add this to your project, and setup accordingly, and Viola, you get your own poor man CI :)

Installation

  $ npm install --save gulp-git-webhook

or

  $ yarn add gulp-git-webhook

Configuration && Usage

Create a js file (normally on your project root directory). Let's call it webhook.js.

const gitWebhook = require('gulp-git-webhook');
const config = {
  "secret": "your-github-webhook-secret",
  "path": "/webhook",
  "port": 8081,
  "branch": "refs/heads/master",
  "cmd": "git pull origin master --no-edit"
};
gitWebhook(config);

If your server is running Linux and support systemd; then you can use generator-nodex to generate a start up file


Then go to your github settings --> webhooks. Supply the configuration parameters:

Payload URL: The url where your server is running (let's use example.com) http://example.com:8081/webhook As you can see the port number 8081 and /webhook correspond the config file, so change it accordingly.

Content type: select application/json

Secret: generate your own secret phrase, again correspond the configuration file.

Which events would you like to trigger this webhook? Just the push event

Active: check this check box so you can see the log from github.

The cmd field is your config is the actual method to run. See table below for more details:

Full configuration properties

| Property name | Description | Default | Type | | ------------- | ------------- | ---------| -----| | secret | A secret key pass to encrypt data between github and your server | '' | String | | path | The path where the web hook call to your server | /webhook | String | | port | The port number where this callback server running on | 8081 | Integer | | branch | The branch where you will trigger action when received event from github | refs/heads/master | String | | cmd | The command to execute when callback happens | git pull origin master --no-edit | String |

Debug option

If you want to know what is happening internally, you can pass NODE_ENV=debug. It will console lot out information.

  NODE_ENV=debug node ./webhook.js

License

MIT © NEWBRAN.CH

Power by generator-nodex.