Current app.js will not run on azure web app about next-express-bootstrap-boilerplate HOT 4 CLOSED

Looks like Azure provides a PORT environment variable which you should use to start your express app.
An easy way for it work would be to write the line start(9001) like this.

start(process.env.PORT || 9001)

It would make sure that the server starts on the PORT env variable (if provided) and would fall back on 9001 if there is no such variable present (such as inside your local environment).

from next-express-bootstrap-boilerplate.

The solution is tested and I can confirm it works! Thanks a bunch.

Would it be possible to implement this in the upstream you are hosting?

Also it might be a good idea to add an echo when the server starts ( Server running on %port or env% with all pistons firing)

Thank you!

from next-express-bootstrap-boilerplate.

Yes, I'm going to put this in in my next commit. (And the server running log)
You're welcome!
Please feel free to close the issue now.

from next-express-bootstrap-boilerplate.

@MustansirZia I reopened this issue to share a small snippet with you for good azure working

In package.json please include the package cross-env

"scripts": {
    "build": "cd app && next build",
    "postinstall": "cd app && next build",
    "start": "cross-env NODE_ENV=production node app.js",
    "dev": "nodemon --ignore app/ app.js"
  },

Also adding the postinstall script is important otherwise Azure web app will not build before a start.

from next-express-bootstrap-boilerplate.