javascript - Configuring 'simplest' node.js + socket.IO + Express server

Question

Realized after setting up a simple node.js socket.IO server that it isn't sufficient to handle even the simplest webpages containing script tags.

So I investigating express which is a simple web framework for node.js.

After looking thru the express documentation http://expressjs.com/guide.html I was still confused as to how I simply combine express with socket.IO on a node.js server.

Couple hours of googling later I came across this tutorial https://www.digitalocean.com/community/articles/how-to-install-express-a-node-js-framework-and-set-up-socket-io-on-a-vps

/**
 * Module dependencies.
 */

var express = require('express')
  , routes = require('./routes')
  , http = require('http');

var app = express();
var server = app.listen(3000);
var io = require('socket.io').listen(server); // this tells socket.io to use our express server

app.configure(function(){
  app.set('views', __dirname + '/views');
  app.set('view engine', 'jade');
  app.use(express.favicon());
  app.use(express.logger('dev'));
  app.use(express.static(__dirname + '/public'));
  app.use(express.bodyParser());
  app.use(express.methodOverride());
  app.use(app.router);
});

app.configure('development', function(){
  app.use(express.errorHandler());
});

app.get('/', routes.index);


console.log("Express server listening on port 3000");
io.sockets.on('connection', function (socket) {
    console.log('A new user connected!');
    socket.emit('info', { msg: 'The world is round, there is no up or down.' });
});

My question is, would anyone reading this configure their server differently? I don't need anything special, no session handling etc, just the ability to serve html pages containing links to external CSS and javascript files.

Answer 1

1. Remove the first app.configure wrapper but leave it's contents. It is useless in general, but especially if you don't pass an argument to it.
2. Remove methodOverride and bodyParser as you aren't using them