Nginx will not handle websockets without some significant work on your part. Go with node-http-proxy, as has been recommended several times now. It is pure node.
Write a simple script which listens on port 80 and proxies each host to the right port. If you're concerned about bringing down and back up the proxy, don't. Just make whatever changes you need to the ruleset, and restart it in the same command on the commandline. Users are as likely to notice that hiccup as to notice you reloading nginx to pick up new rules. On Sun, Apr 8, 2012 at 8:54 AM, Alan Hoffmeister <[email protected]>wrote: > @Lothar, yes, that was a solution that I was exploring, but shutting > down all websites for adding one more it's quite perturbing.. > After researching a bit, I'm start convincing myself that I'll need > Nginx to reverse proxy webites on the same host but running node in > diferent ports. > > I was hopping that I could find some solution 100% Node.js :( > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- chrisrhoden -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
