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

probiotic

v1.0.3

Published

The simplified multi-workers daemon

Downloads

7

Readme

probiotic

The simplified multi-workers daemon

NPM Downloads NPM Version GitHub Tag GitHub License Dependencies Status

(For a featureful cousin of Probiotic see Progenic)

Table of Contents

Getting Started

Install the module with: npm install probiotic
Then use it in your code to start a service with as many workers as needed:

const probiotic = require('probiotic');

probiotic.run({
    name:         'myServiceName',
    main:         'path/to/myServiceScript.js',
    logsBasePath: '/mnt/logs-volume',
    workers:      4
});

Requirements

Probiotic requires NodeJS 4.5.0+ and can be istalled via NPM:

npm install probiotic
# or:
npm install --save probiotic

Options

The mandatory name parameter is the name the service will be started with. It affects the process' PID file name (under /var/run) as well as the log files names.

The mandatory main parameter points to the JS file that is actually the service code.
This code will be spawned exactly workers-times in different processes children of the service containing the probiotic code.

The optional workers parameter tells probiotic how many workers ave to be spawn. When omitted probiotic will assume the value 'auto', spawning exactly require('os').cpus().length - 1 workers (i.e. the number of CPUs of the system minus 1).

The optional logsBasePath parameter specifies the path where log files are created. By default your service will have log files created under /var/log.
Probiotic will create one log file for the master process and one for each of the children workers.