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

cluster_master

v0.1.1

Published

Easy cluster management + zero downtime deploys & reloads

Downloads

3

Readme

ClusterMaster

Basic cluster management in one line:

return if require('cluster_master').runMaster()
# worker's code here

By default it'll spawn os.cpus().length workers and respawn every dead worker.

Out of box you'll get safe zero downtime reload:

  • send SIGHUP to process
  • cluster will try to spawn new worker
  • if new worker is ok then cluster will gracefully close one running worker & 'll reload all old workers
  • if new forker failed it won't destroy old workers

For more stuff see source.

Use forever

Oops! Seems like forever still does not have proper support for specifying kill signal.

However you can specify pid file for ClusterMaster and hups yourself:

return if require('cluster_master').runMaster(pidfile: 'pids/cluster.pid')

May be later: Once cluster is started with forever

forever start -c coffee server.coffee

it can be reloaded with

forever stop --killSignal SIGHUP -c coffee server.coffee