
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
cluster_master
Advanced tools
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:
SIGHUP to processFor more stuff see source.
Oops! Seems like forever still does not have proper support for specifying kill signal.
However you can specify pid file for ClusterMaster and send 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
MIT
FAQs
Easy cluster management + zero downtime deploys & reloads
We found that cluster_master demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.