adding some debug code to see why connect-mongo is failing to retriev…

…e session on heroku only
froggeric · Sep 14, 2015 · 3c1aad4 · 3c1aad4
1 parent 8083451
commit 3c1aad4
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 2 deletions.
diff --git a/app/gameserver.js b/app/gameserver.js
@@ -85,6 +85,9 @@ module.exports = function(server, sessionStore) {
  return;
  }
  User.findById(session.passport.user, function(err, currentUser) {
+ if(err) {
+ console.log("user retrieval failed - error: " + err);
+ }
  if(userToSocket[currentUser._id]) {
  userToSocket[currentUser._id].push(socket);
  } else {

diff --git a/package.json b/package.json
@@ -15,7 +15,7 @@
  "passport-twitter": "~1.0.2",
  "passport-google-oauth": "~0.1.5",
  "connect-flash": "~0.1.1",
- "connect-mongo": "~0.4.1",
+ "connect-mongo": "~0.8.2",
  "bcrypt-nodejs": "latest",
  "tunnel": "0.0.3",
  "socket.io": "~1.0.6",

diff --git a/server.js b/server.js
@@ -48,7 +48,7 @@ var MongoStore = require('connect-mongo')(session);
 // https://github.com/kcbanner/connect-mongo/issues/80
 var sessionStore = new MongoStore({
  url: configDB.url,
- autoReconnect: true
+ auto_reconnect: true
 });
 
 mongoose.connect(configDB.url); // connect to our database