3 ms·
What were people using previously? Just plopping their node.js or whatever straight on the network?
by davidw 14y ago
What were people using previously? Just plopping their node.js or whatever straight on the network?
- istvanp 14y agoWe are using HAproxy to direct traffic and nginx only as a web server. The config looks something like this: http://stackoverflow.com/a/8640394/218413 http://stackoverflow.com/a/8640394/218413
- adamkittelson 14y agoSomething like varnish or haproxy. In my setup I had varnish proxying "/websocket" directly to my app server, and everything else to nginx.
- brendanobrien 14y agoI've been using HAProxy in the interim.
- jsharpe 14y agoI use python's Tornado webserver directly on the network. Don't know if it's the best idea, but seems to work fine for my purposes.
- dcraw 14y agoI've had good results so far with node-http-proxy: https://github.com/nodejitsu/node-http-proxy/ https://github.com/nodejitsu/node-http-proxy/ Easy to set up, and has the benefit of reducing the number of processes I need to maintain (my node server and my proxy server are the same).
- mason55 14y agoHey... saw your comment here http://news.ycombinator.com/item?id=5172775 http://news.ycombinator.com/item?id=5172775 about the work you did on unrolling arrays in mongo_fdw. Any chance you can email me about it (that thread is closed). username @ gmail.com
- churreiro 14y agoVarnish and HAproxy
- pkulak 14y agoHAProxy has had Websocket support for a while now. But other than that, you can run run on the same domain without a proxy by just using a different port.
- elliotanderson 14y agoThere was two main options 1. Run nginx with something like HAProxy/Varnish infront 2. Run nginx alone with the app server on port 80/443 and the websocket server running on a special port. The app was then proxyed using the built in http_proxy, while the websocket was handled by tcp_proxy.