z1
Node.js cluster manager
Last updated a year ago by robojones .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install z1 -g
SYNC missed versions from official npm registry.

z1

CircleCI

Maintainability Test Coverage

z1 is a Node.js cluster management program. It works on Linux Debian, Ubuntu, and other Debian based distributions.

When using Node.js on a web server, one will somehow come to the point where he wants to start multiple processes for one app. The main goal of z1 is to simplify the creation and management of Node.js processes.

Terminal example

This animation shows how simple it is to start a Node.js application with z1.

Table of contents

Changes

  • v4.0.0
    • use revents for data transmission between the CLI and the daemon.
    • Ctrl + C can now be used to abort the starting process of apps.
    • remove upgrade command.
  • v3.17.0
  • v3.16.0
    • add colors to cli
  • v3.15.0
    • display the app's logs during command execution
  • v3.14.0
    • add JSDoc to API

Setup

Installation

Via NPM

sudo npm install z1 -g

Note: You might want to run z1 resurrect automatically after rebooting your system. It will start the z1 daemon and all the apps that were running before. (see: install command)

Prepare package.json

Before you can start your Node.js app, you need to add a few things to your package.json file.

  1. name - The name of your app.
  2. main - The entry point of your app (The file that you would normally run with (node <file>).
  3. ports (optional) - An array of port numbers that your app uses.
  4. workers (optional) - A number specifying how many processes should be created for your app. The default value is the number of CPU-cores in your system.
  5. output (optional) - A directory for the log and error files. (Default: ~/.z1/<yourAppname>)
  6. devPorts (optional) - Ports for development
  7. devWorkers (optional) - Workers for development

Important: z1 needs to know when your Node.js program (e.g. a web server) is successfully started. If you app uses ports, z1 will automatically know when it listens to all the specified ports. It will then assume, that you app is completely started. If you app does not use any ports, you must require z1 in your program and call the z1.ready() method.

Example package.json file:

{
  "name": "homepage",
  "main": "index.js",
  "ports": [8080],
  "workers": 2
}

Development

If you are running z1 locally, you can set NODE_ENV=development. This will cause z1 to use the devPorts and devWorkers (if specified) instead of the ports and workers properties from the package.json. The default timeout for stop and restart will be set to 0ms.

CLI

Environment variables

You can set different environment variables for each app. The start command automatically applies the environment variables of the current shell to the app.

EXAMPLE=hello z1 start path/to/your/app

There are some environment variables that automatically z1 sets for each process:

  • PORT - The first port you specified.
  • PORTS - All ports that your app uses (separated by commas).
  • APPNAME - The name of your app.
  • PWD - The directory of your app.
  • WORKERS - The number of workers started for the app.

These variables can't be overwritten.

Start

After you prepared the package.json file of your app, you can now start it. First go to the directory where the package.json of your project is located. Type the following command into your terminal:

z1 start

This command works regardless of how many workers you have specified in the package.json file. If your app was successfully startet, the output should look like this:

Start command output

As you may have noticed, each log is displayed twice. This happens because two workers are started for the app and the logs of all workers are being displayed.

Options

If you want to start your app with different settings than the ones specified in the package.json, you can add them to to the z1 start command.

--name anotherName
--ports 80,2020,8080
--workers 4
--output path/to/logs/

Restart

You can restart your app to apply updates for your app or changes to the package.json. The restart process will be gapless and no requests will be refused. Just type the following command:

z1 restart homepage

The first argument for the z1 restart command is the name that was specified in the package.json when you started the app. If you are running this command inside the directory of the Node.js application, z1 will automatically detect the name.

Output of the example from above:

Restart command output

Options

--timeout 10000

--timeout is a number specifying the maximal time (in ms) that the old workers can continue to run after they are killed. The timeout allows old processes to finish their active requests while not accepting new ones. If all requests are finished, or the timeout is exceeded, the old processes get killed. The default value is 30000 (30s). If you set it to "Infinity" the old processes might run forever.

List

z1 list

Displays a list of all running apps.

The output could look like this:

List command output

Info

z1 info homepage

Shows more detailed information than z1 list.

Example output:

Info command output

  • pending - processes are currently starting.
  • available - workers are listening to all the ports specified in the package.json
  • killed - workers are not listening for new connections. They will finish their outstanding requests before they exit.
  • revive count - shows you how often the workers of your app crashed since the last restart.

Options:

  • --name - output the appname
  • --dir - output the directory of the app
  • --ports - output the ports that the app uses
  • --pending - output the number of pending workers
  • --available - output the number of available workers
  • --killed - output the number of killed workers
  • --revive-count - output how often the app has been revived

Stop

To stop an app just type:

z1 stop homepage

Example output:

Stop command output

Options

--timeout 10000

--timeout is a number specifying the maximal time that the workers are allowed to run after they are killed (in ms). The default value is 30,000ms. If you set it to "infinity" the old processes might run forever.

Exit

z1 exit

This will kill the z1 daemon process and therefore all apps and workers.

Resurrect

After you typed exit, you can use the following to start all the apps that were running before:

z1 resurrect

Note: If you are starting a new app before z1 resurrect, the old apps will not be restored.

Install and Uninstall

This command allows you to add and remove additional features.

  1. zsh - shell completion for zsh
  2. bash - shell completion for bash (coming soon)
  3. cron - cron job that resurrects z1 after a reboot
sudo z1 install zsh

Passing arguments to workers

You can start your app with custom arguments.

z1 start --name 'custom app' --ports 80 -- hello

This would start an app with the name 'custom app' that is listening on port 80. Everything behind the -- will be passed to the workers. In your code you can get the "hello" as argv.

process.argv[2] === 'hello' // true

API

Besides the CLI, you can also require z1 to control your apps with a Node.js program.

const z1 = require('z1')

z1.start(dir, args, opt, env, immediate)

Arguments

  • dir <String> - Path to the directory where the package.json of the app is located (Default: current directory)
  • args <Array> (optional) - Arguments for the workers
  • opt <Object> (optional) - Options that overwrite the ones from the package.json
  • env <Object> (optional) - Key-value-pairs to be added to process.env in the workers.
  • immediate <Boolean> (optional) (Default: false)

Returns a <Promise> that gets resolved when the app is started. If you set immediate to true, the promise gets resolved immediately after your command was transmitted to the daemon.

By default It resolves to an object with the following data:

{
  app: String,
  dir: String,
  started: Number
}
  • app - The name of the app specified in the package.json. You will need this in order to restart/stop the app.
  • dir - Absolute path to the directory where the package.json is located
  • started - Number of workers started for this app

z1.restart(app, opt, immediate)

Arguments

  • app <String> - The name specified in the package.json of the app you want to restart.
  • opt <Object> - (optional)
    • timeout <Number> - Maximum time until the old workers get killed (default: 30000ms).
    • signal <String> - Kill signal for the old workers
  • immediate <Boolean> (optional) (Default: false)

Returns a <Promise> that gets resolved when the new workers are available and the old ones are killed. It resolves to an object with the following data:

{
  app: String,
  dir: String,
  started: Number,
  killed: Number
}
  • app - the app name
  • dir - directory of the app
  • started - Number of started workers
  • killed - Number of killed workers

z1.stop(app, opt, immediate)

Arguments

  • app <String> The name specified in the package.json of the app you want to restart.
  • opt <Object> (optional)
    • timeout <Number> Maximum time until the old workers get killed (default: 30000ms).
    • signal <String> Kill signal
  • immediate <Boolean> (optional) (Default: false)

Returns a <Promise> that gets resolved when the old workers are killed. It resolves to an object with the following data:

{
  app: String,
  killed: Number
}
  • app - the app name
  • killed - Number of killed workers

z1.info(app)

Arguments

  • app <String> The name of your app.

Returns a <Promise> that gets resolved to an object that contains information about the app.

Example:

{
  name: 'homepage',
  reviveCount: 0,
  ports: [80],
  pending: 0,
  available: 2,
  killed: 0
}

z1.list()

Returns a <Promise> that resolves to an object containing data about all running workers.

You can access the data for an app by using the name as key:

z1.list().then(data => {
  console.log(data.stats)
})

The output would be:

{
  homepage: {
    dir: '/home/user/apps/homepage',
    ports: [80],
    pending: 0,
    available: 2,
    killed: 0
  }
}

z1.exit()

Returns a <Promise> that resolves to an empty object. It gets resolves after the z1 daemon has exited.

z1.resurrect(immediate)

  • immediate <Boolean> (optional) (Default: false)

Returns a <Promise> that resolves to an object.

Example:

{
  started: 2 // two workers started
}

It will be rejected if z1.resurrect() or z1.start() was called before.

Resurrect will start all apps that were running before the daemon was killed.

z1.ready()

Returns a <Promise> that resolves when the ready signal has been transmitted.

This function must be called if an app does not use any port. It will tell the z1 daemon that your app has been started successfully.

Example:

const z1 = require('z1')

// ...your program...

z1.ready()

Current Tags

  • 4.1.1                                ...           latest (a year ago)

112 Versions

  • 4.1.1                                ...           a year ago
  • 4.1.0                                ...           2 years ago
  • 4.0.0                                ...           3 years ago
  • 4.0.0-0                                ...           3 years ago
  • 3.17.3                                ...           3 years ago
  • 3.17.2                                ...           3 years ago
  • 3.17.1                                ...           3 years ago
  • 3.17.0                                ...           3 years ago
  • 3.16.8                                ...           3 years ago
  • 3.16.7                                ...           3 years ago
  • 3.16.6                                ...           3 years ago
  • 3.16.5                                ...           3 years ago
  • 3.16.4                                ...           3 years ago
  • 3.16.3                                ...           3 years ago
  • 3.16.2                                ...           3 years ago
  • 3.16.1                                ...           3 years ago
  • 3.16.0                                ...           3 years ago
  • 3.15.0                                ...           3 years ago
  • 3.15.0-0                                ...           3 years ago
  • 3.14.1                                ...           3 years ago
  • 3.14.0                                ...           3 years ago
  • 3.13.1                                ...           3 years ago
  • 3.13.0                                ...           3 years ago
  • 3.12.3                                ...           3 years ago
  • 3.12.2                                ...           3 years ago
  • 3.12.1                                ...           3 years ago
  • 3.12.0                                ...           3 years ago
  • 3.11.0                                ...           3 years ago
  • 3.8.1                                ...           3 years ago
  • 3.8.0                                ...           3 years ago
  • 3.7.6                                ...           3 years ago
  • 3.7.5                                ...           3 years ago
  • 3.7.4                                ...           3 years ago
  • 3.7.3                                ...           3 years ago
  • 3.7.2                                ...           3 years ago
  • 3.7.1                                ...           3 years ago
  • 3.7.0                                ...           3 years ago
  • 3.7.0-0                                ...           3 years ago
  • 3.6.2                                ...           3 years ago
  • 3.6.1                                ...           3 years ago
  • 3.6.0                                ...           3 years ago
  • 3.5.1                                ...           3 years ago
  • 3.5.0                                ...           3 years ago
  • 3.4.2                                ...           3 years ago
  • 3.4.1                                ...           3 years ago
  • 3.4.0                                ...           3 years ago
  • 3.3.10                                ...           3 years ago
  • 3.3.9                                ...           3 years ago
  • 3.3.8                                ...           3 years ago
  • 3.3.7                                ...           3 years ago
  • 3.3.6                                ...           3 years ago
  • 3.3.5                                ...           3 years ago
  • 3.3.4                                ...           3 years ago
  • 3.3.4-0                                ...           3 years ago
  • 3.3.3-0                                ...           3 years ago
  • 3.3.2-0                                ...           3 years ago
  • 3.3.1-0                                ...           3 years ago
  • 3.3.0-0                                ...           3 years ago
  • 3.2.2                                ...           3 years ago
  • 3.2.1                                ...           3 years ago
  • 3.2.0                                ...           3 years ago
  • 3.1.41                                ...           3 years ago
  • 3.1.40                                ...           3 years ago
  • 3.1.39                                ...           3 years ago
  • 3.1.38                                ...           3 years ago
  • 3.1.37                                ...           3 years ago
  • 3.1.36                                ...           3 years ago
  • 3.1.35                                ...           3 years ago
  • 3.1.34                                ...           3 years ago
  • 3.1.33                                ...           3 years ago
  • 3.1.32                                ...           3 years ago
  • 3.1.31                                ...           3 years ago
  • 3.1.30                                ...           3 years ago
  • 3.1.29                                ...           3 years ago
  • 3.1.27                                ...           3 years ago
  • 3.1.26                                ...           3 years ago
  • 3.1.25                                ...           3 years ago
  • 3.1.24                                ...           3 years ago
  • 3.1.23                                ...           3 years ago
  • 3.1.22                                ...           3 years ago
  • 3.1.21                                ...           3 years ago
  • 3.1.20                                ...           3 years ago
  • 3.1.19                                ...           3 years ago
  • 3.1.18                                ...           3 years ago
  • 3.1.17                                ...           3 years ago
  • 3.1.16                                ...           3 years ago
  • 3.1.14                                ...           3 years ago
  • 3.1.13                                ...           3 years ago
  • 3.1.12                                ...           3 years ago
  • 3.1.11                                ...           3 years ago
  • 3.1.10                                ...           3 years ago
  • 3.1.9                                ...           3 years ago
  • 3.1.8                                ...           3 years ago
  • 3.1.7                                ...           3 years ago
  • 3.1.6                                ...           3 years ago
  • 3.1.5                                ...           3 years ago
  • 3.1.4                                ...           3 years ago
  • 3.1.3                                ...           3 years ago
  • 3.1.2                                ...           3 years ago
  • 3.1.1                                ...           3 years ago
  • 3.1.0                                ...           3 years ago
  • 3.0.2                                ...           3 years ago
  • 3.0.1                                ...           3 years ago
  • 3.0.0                                ...           3 years ago
  • 2.0.4                                ...           3 years ago
  • 2.0.3                                ...           3 years ago
  • 2.0.2                                ...           3 years ago
  • 2.0.1                                ...           3 years ago
  • 2.0.0                                ...           3 years ago
  • 1.0.2                                ...           4 years ago
  • 1.0.1                                ...           4 years ago
  • 1.0.0                                ...           4 years ago
Maintainers (1)
Downloads
Today 0
This Week 0
This Month 115
Last Day 0
Last Week 2
Last Month 1
Dependencies (8)
Dev Dependencies (6)
Dependents (0)
None

Copyright 2014 - 2016 © taobao.org |