Skip to content
Node powered Rack server
CoffeeScript Ruby JavaScript
Latest commit d523cc8 @josh nack 0.16.0
Failed to load latest commit information.
bin Use new connect api
doc Update doc manifest
lib Attempt to load json after config
man Rebuild man pages
src Remove old multiple header hack
test Server tests use JSON const directly
.gitignore Upgrade to netstring 0.2
.npmignore Don't ignore .git*
.travis.yml Test on node 0.10.x
Cakefile Add pretest
LICENSE Initial commit Require node 0.6
Rakefile Ensure lib is in path
index.js Flatten namespace
package.json nack 0.16.0

nack -- Node powered Rack server


nack is a Rack server built on top of the Node.js HTTP server. Node does all the hard work of accepting and parsing HTTP requests and nack simply passes it along to a Ruby worker process as a serialized object. You can read more about how the [IPC protocol][nack-protocol(7)] works. Besides running as a standalone Rack server, you can use the JS API to run multiple apps from the same Node process.


Simple proxy

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

var app = nack.createProcess("/path/to/app/");

http.createServer(function (req, res) {
  app.proxy(req, res);
}).listen(8124, "");

You can spawn up a pool of workers with:

var nack = require('nack');
nack.createPool("/path/to/app/", { size: 3 });

Workers can idle out after a period of inactivity:

// Timeout after 15m
nack.createPool("/path/to/app/", { idle: 15 * 60 * 1000 });

Theres a more friendly server API that returns a Connect application.

var connect = require('connect');
var nack    = require('nack');



You can grab the package from npm.

npm install nack


  • node >= 0.6.x
  • node-netstring
  • rack
  • json


nack was design to be used as a local development proxy. You probably don't wanna try running a production app on it. I'm sure its slow too so don't send me any benchmarks.


Copyright (c) 2010 Joshua Peek.

Released under the MIT license. See LICENSE for details.


nack(1), nack-protocol(7), nack-server(3), nack-pool(3), nack-process(3)

Something went wrong with that request. Please try again.