The joke is on us today. We have been joking around the whole day about all the bugs we had in our project. “No, it is not a bug. It is a feature.”

Until, we ran into this classical *** undefined is not a function bug after deploying our app to Nodejitsu. It took Hao and me a while to find out that, much to our surprise, the filesystem on Mac OS is case insensitive by default. AND, according to this Stack Exchange article, “this is not a bug. It is a feature of the file system”.

One of our JavaScript file’s camelCase was off by a letter. It works fine in Mac because it is case insensitive, but it doesn’t work in a Linux environment because it is case sensitive.

Now I am worried about all the other places that the same type of bugs might exist.

There are many ways to store sessions in Express.js, including:
– Memory
– Traditional database
– In memory database

Our group project is using MongoDb to store session. The code is:

  var express = require('express');
  var mongoose = require('mongoose');
  mongoose.connect('mongodb://myuser:mypass@localhost:27017/mydb');
  var MongoStore = require('connect-mongo')(express);
  app.use(express.session({
    store: mongoStore(new MongoStore({ db: mongoose.connection.db })),
    secret:"changeme"
  }));

If we are going to use Redis, the code would look like(?):

var RedisStore = require('connect-redis')(express);
app.use(express.session({
  store: new RedisStore({host: 'localhost', port: 3000, client: redis}),
  secret: "changeme"
}));

Do we have to turn on cookie to support session? The answer must be yes.
A good article to read: http://stackoverflow.com/questions/5522020/how-do-sessions-work-in-express-with-nodejs/11585839#11585839

// pass a secret to cookieParser() for signed cookies
app.use(express.cookieParser('manny is cool'));

// add req.session cookie support
app.use(express.cookieSession());

We run into the Linkedin API throttle limit so quickly…. Needs to find a way to cache our results.

Time flies. I can’t believe it is already ten weeks after the program starts. It seems like that the ten weeks is just a long working day to me….

The hiring day is coming up in ten days. Better get ready for it

Sigh…

Wanted to deploy to Nodejitsu, but can’t get the bower install to work.

Basically, our app has two package management systems, npm and bower. While Nodejitsu supports npm, it doesn’t seem to support bower.

I tried to do this:

var bower = require('bower'),
path = require('path');

bower.commands
.install(['underscore'])
.on('end', function(installed) {
console.log(installed);
});

With this in my package.json:

  "scripts": {
    "predeploy": "echo Before deploying!",
    "postdeploy": "node ./bower_install.js",
    "start": "node ./start.js"
  }

Can’t get it to work. Following the advice from this url: http://stackoverflow.com/questions/16795677/nodejitsu-and-bower-install/16796998#16796998