Nginx (serving html) and Node.js setup

Question

I was thinking of building a web app which would be single page, using only javascript to update the page (no reloads). So I'm confused about what kind of setup to use.

I'm kinda new to both technologies, so I was wondering if you can set up nginx to serve html (+ js, css and other static resources) like a normal web server and then from those pages connect to a node.js websocket server (same host/ip) using something like socket.io?

Is this setup good or bad? What would be a better approach? What advantage would I get if I serve html pages in node.js and get static resources (css, js, images, ...) from nginx?

FUD · Accepted Answer · 2012-04-12 19:23:25Z

3

I dont think serving few images and static htmls from nodejs itself will ever be a bottleneck , ideally a front end proxy like nginx is required if you need to load balance between multiple servers and also for exposing you internal http services as https traffic. If you dont have that requirement it would be a overkill imho.

edited Apr 12, 2012 at 19:23

answered Apr 12, 2012 at 19:06

FUD

5,2147 gold badges42 silver badges63 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

Matjaz Muhic Over a year ago

I was thinking of that primarly because of decoupling. So I could have websockets-only node.js app. So doing both http and websockets in one app is more than ok? I really don't want it to grow into a big ball of mud.

FUD Over a year ago

Just to let you know before you dive too deep...nginx still has no support for websockets :)..

Matjaz Muhic Over a year ago

I know. Maybe the whole nginx idea from the start was a little over engineered... :)

FUD Over a year ago

well as far as decoupling is concerned you can have your websocket traffic connect to a different port (one on which socket.io runs) from your simple html server's pages

FUD Over a year ago

AND if you reaaaallly have to go for a proxy there is a good option ...github.com/nodejitsu/node-http-proxy

|

Tracker1 · Accepted Answer · 2012-04-12 19:55:02Z

1

From various comments in the currently accepted answer, I wanted to note the following.

NodeJS itself does a pretty decent job of delivering static content, as good as nginx in many cases.

Trying to proxy a WebSocket connection is problematic at best currently, as most proxy code simply doesn't support it. Currently, it is best to use Node directly.

If/When you have a need to deliver static content separately, best to use another domain and a CDN at that point.

answered Apr 12, 2012 at 19:55

Tracker1

19.4k12 gold badges85 silver badges106 bronze badges

Collectives™ on Stack Overflow

Nginx (serving html) and Node.js setup

2 Answers 2

6 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

6 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related