js-cgi - Javascript CGI process manager

js-cgi is a javascript CGI process manager, similar to php-fpm, for executing node.js scripts behind NGINX or Apache. Comes in handy if you want to run PHP along side node.js or if you don’t want to write your own web server into your node.js application.

Dependencies:

• express.js

Configuration:

On startup, js-cgi will look for a config file called js-cgi.config in the same folder as the js-cgi.js file. If it’s not found it will use the defaults.

Example:

module.exports = {
   port:3000,
   localhostOnly:true,
   workers:2
};

• port - Indicates which TCP port to listen on. default=3000
• localhostOnly - Prevents remote agents from invoking scripts. default=true
• workers - Number of worker processes. default=the number of processors on the local machine.

Usage:

Add a directive to your nginx.conf file. Using an “njs” extension on the server javascript files instead of a “js” extension will enable NGINX to distinguish server scripts from browser javascript files.

location ~ [^/]\.njs(/|$) {
   proxy_pass   http://localhost:3000;
   proxy_set_header X-Real-IP $remote_addr;
   proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
   proxy_set_header Host $http_host;
   proxy_set_header X-NginX-Proxy true;
   proxy_set_header path_translated $document_root$fastcgi_path_info;
}

Middleware

If you want to use express.js middleware, create a “use.js” file and save it to the same folder as the js-cgi app like so:

var bodyParser = require('body-parser'),
    cookieParser = require('cookie-parser'),
    fileUpload = require('express-fileupload');
module.exports = function(app){
  app.use(fileUpload());//for uploading files
  app.use(bodyParser.json()); // for parsing application/json
  app.use(bodyParser.urlencoded({ extended: true })); // for parsing application/x-www-form-urlencoded
  app.use(cookieParser());// for parsing cookies
}

Once you configure and restart NGINX, you can start js-cgi.

node js-cgi.js