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 🙏

© 2025 – Pkg Stats / Ryan Hefner

propagit-f

v0.6.11

Published

cascading multi-server git deployment

Readme

propagit

Cascading multi-server git deployment.

build status

example

First start up a hub server to listen for git deploys:

$ propagit hub --port=6000 --secret=beepboop
control service listening on :6000
git service listening on :6001

then spin up as many drones as necessary on other machines with the command to run on deployment for each type of service:

$ propagit drone --hub=hubhost:6000 --secret=beepboop

Now you can git push to the hub and the drones will git fetch from the hub. Just do:

$ cd ~/projects/somerepo
$ git push http://hubhost:6001/somerepo master

First deploy the code to a fresh deploy directory for the given repo name and commit hash:

$ propagit deploy --hub=hubhost:6000 --secret=beepboop \
  somerepo ed56c6e85731d412fe22cf437cb63130afc34b07

then spawn processes for that deployment:

$ propagit spawn --hub=hubhost:6000 --secret=beepboop \
  somerepo ed56c6e85731d412fe22cf437cb63130afc34b07 \
  -- node server.js 8085

usage

Usage:
  propagit OPTIONS hub

    Create a server to coordinate drones.

    --port       port to listen on
    --secret     password to use
    --basedir    directory to put repositories

  propagit OPTIONS drone

    Listen to the hub for deploy events to execute commands with
    environment variables $REPO and $COMMIT set on each deploy.
 
    --hub        connect to the hub host:port
    --secret     password to use
    --basedir    directory to put repositories and deploys in
  
  propagit OPTIONS deploy REPO COMMIT
  
    Deploy COMMIT to all of the drones listening to the hub.

    --hub        connect to the hub host:port
    --secret     password to use
  
  propagit OPTIONS spawn REPO COMMIT [COMMAND...]
  
    Run COMMAND on all the drones specified by OPTIONS.
    $PROCESS_ID and $DRONE_ID will be set for every spawned process.
    Note that $PROCESS_ID is not the system PID value.

  propagit OPTIONS ps
  
    List all the running processes on all the drones.

methods

var propagit = require('propagit')

var p = propagit(opts)

Create a new propagit object with opts:

  • secret - authenticate with this passphrase
  • hub - if specified, connect to this hub

p.drone()

Register with the connected hub as a drone.

p.listen(controlPort, gitPort)

Create a new hub on controlPort and start a git http server on gitPort.

p.use(fn)

Modify the dnode server or client service with fn(service).

In server mode the fn also gets a conn object: fn(service, conn).

install

With npm do:

npm install -g propagit