Debugging a total failure of a Hello World node.js demo!

Sign in to queue

Description

Scott messes up a node.js demo then spends the next 30 minutes debugging it, learning more about Azure in the process!

Embed

Download

Download this episode

The Discussion

  • User profile image
    JeroenH

    I think the problem actually wasn't the missing server.js. If you look carefully, the last commit deleted *2* files and also changed one. I'm would guess there lies the key...

  • User profile image
    SyntaxC4

    Windows Azure Web Sites adds a web.config to your deployment which wires up iisnode to look for server.js. Your express package was saying that your application start file was app.js

    another way to fix this would be to modify the web.config to point to app.js, this way if server.js was still required for your application to run iisnode would use app.js as your application entry point and server.js could still be referenced from your code.

Add Your 2 Cents