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

herd

v1.0.0

Published

A simple wrapper over node cluster for zero-downtime reloads

Downloads

821

Readme

herd

Herd your child processes! A simple wrapper over node cluster for zero-downtime reloads.

Quickstart

Just pass herd the function to run on the child-processes.

var http = require('http');
var herd = require('herd');

herd('server')
  .run(function (){
    http.createServer.listen(8000);
  });

From the terminal, send a SIGHUP signal to gracefully reload the process:

$ kill -1 1922

We usually keep the master process really small, and never restart it. By default the process will exit after 1 second, but close handlers and custom timeouts can be specified as well.

API

Herd(name)

Create a new herd with title name

.timeout(ms)

Set the timeout before killing a worker in ms. (defaults to 1 second if you don't specify a close handler, otherwise none).

.server(isServer)

By default, new processes will not be created until a listening event is emitted by the child process (which is the default for servers). Call this flag if you'd rather wait for online event, in the case of your workers which might not ever call net.Server.listen.

.size(workers)

Set the number of workers to spawn. Defaults to the number of cpus.

.close(fn)

Calls the fn as the worker is as part of the exit handler. Which can be used to perform some type of cleanup before exiting. If a timeout is also specified, the process will exit whenever the first condition is triggered.


/**
 * Flush our remaining messages to disk.
 */

function close(fn){
  flush(msgs, fn);
}


herd()
  .close(close)
  .run(run);

License

(The MIT License)

Copyright (c) 2012 Segment.io <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.