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

gitdeploy

v1.0.6

Published

Listen for git web hooks and automatically update and deploy code

Downloads

19

Readme

gitdeploy

Listen for git web hooks and automatically update and deploy code.

Install

The source is available for download from GitHub. Clone the repository, copy config.local.js.orig to config.local.js and edit it to suit your needs (see below). Run npm install to install dependencies, then run node index.js and confirm the service successfully starts. Although the service should be stable, you will probably want to run it via a process supervisor such as pm2, monit, forever, supervisord, etc.

Configuration

  • web_port - The HTTP port to listen to. Default is 23200.
  • run_as_user - Switch the process to another user after it has started. This is useful for running as root and logging to ie /var/log/gitdeploy.log, then dropping root privileges. Defaults to empty.
  • log_path - Relative or absolute path for the log file. Defaults to gitdeploy.log.
  • log_level - Logging verbosity. Valid values are debug, info, warn, and error. Defaults to debug.
  • forward_to - An optional array of URLs to forward incoming pings to. Useful for pinging servers that are not publicly accessible.
  • repositories - An array of repository objects describing local git clones. Each repository object consists of the following fields:
    • url - Public web URL of the repository. This must match what GitHub/Bitbucket/etc send exactly. An example is https://github.com/jhurliman/Test-Repo.
    • path - Local path to the cloned repository. This must be an absolute path.
    • deploy - (Optional) A script or shell command to run after git pull has finished. This is usually a deployment or notification script.