I would like some guide for deploying multiple hosts on the same machine,
Haibu seems to do the trick very well, where can I find some extended
documention about it?
Thanks!
Em sábado, 7 de abril de 2012, Erich Kolb escreveu:
> What would you like to know?
>
>
>
> *From:* nodejs@googlegroups.com
I work with sub domains on my live and test systems, but with single
host on my dev and sandbox systems.
I use express as the web framework and my first route is something
like this:
app.get('*', function(req, res, next) {
var host = req.headers.host;
var url = req.url;
if (host === env.vHo
Sry mlegenhausen, some seconds after I sent the email I could read that
it's just a matter os selecting a db on the connection string ;)
Em quinta-feira, 12 de abril de 2012, mlegenhausen escreveu:
> @alan Why you want to do that? You also normally don't run several MySQL
> instances for each si
This is very interesting. I always though that Node developers use
Nginx in their stack for proxying. But reading the docs, node-http-
proxy is mentioned as battle-hardened. How does this hold up when one
serves images? Is the performance comaparable? Nginx is alleged to be
almost unbeatable at ser
Ok, but I am still not sure about 2 things.
1. I read that node-http-proxy does not work with the body parser
middleware. How is one supposed to handle forms and other things then?
I have my app configured as follows:
app.use(express.bodyParser({ keepExtensions: true, uploadDir:
__dirname + "/pu
Ok, so that means I leave the bodyParser middleware config out of the
node-proxy config? What I meant by my typical use case is this:
# Vhosts
apps A1 on port 8001, A2 on port 8002 are load balanced and serves --
> www.domainA.com
app B:9001, B2:9002 are also load balanced and serving requests fo
Great! Thanks Chris!
On Apr 13, 6:36 pm, Chris Rhoden wrote:
> On Fri, Apr 13, 2012 at 12:01 PM, akira wrote:
> > Ok, so that means I leave the bodyParser middleware config out of the
> > node-proxy config?
>
> Yes.
>
> > What I meant by my typical use case is this:
>
> > # Vhosts
> > apps A1 o
I spoke too soon, excuse for my "newbieness" but the docs are not
making things easier, why isnt an API list somewhere?
>From the examples page on github, I want to combine this config for
simple reverse-proxying
var options = {
hostnameOnly: true,
router: {
'foo.com': '127.0.0.1:8001',
Create a second proxy that does the load balancing for you and redirect
from the first proxy to your balancing proxy. The idea is to build a
hierarchy of proxies.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You r
Perhaps I am missing something but I have not had any issues using
nginx 1.1.18 proxying for a node server using Socket.IO.
See https://github.com/LearnBoost/socket.io/issues/696#issuecomment-5038048
On Apr 8, 8:19 am, Chris Rhoden wrote:
> Nginx will not handle websockets without some significa
On Apr 14, 2:25 pm, Dave wrote:
> Perhaps I am missing something but I have not had any issues using
> nginx 1.1.18 proxying for a node server using Socket.IO.
It depends on the browser too. I don't know if nginx 1.1.18
specifically added support for older WebSocket specs (draft 75 or 76),
but th
I found another solution, Vost. It supports both Vhosts and load
balancing
https://github.com/kommander/vost
On Apr 14, 11:25 pm, mscdex wrote:
> On Apr 14, 2:25 pm, Dave wrote:
>
> > Perhaps I am missing something but I have not had any issues using
> > nginx 1.1.18 proxying for a node server
you can use node-http-proxy as your front-facing server - look at the
examples. It has been pretty solid.
On 04/07/2012 01:38 AM, Alan Hoffmeister wrote:
I would like some guide for deploying multiple hosts on the same
machine, Haibu seems to do the trick very well, where can I find some
exte
@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 t
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 bac
did you saw the npm site-manager ?
Em domingo, 8 de abril de 2012 10h19min30s UTC-3, chrisrhoden escreveu:
>
> 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
Ok guyz, node-http-proxy just did it, awesome!
Now I have a multi website server running 100% javascript, whit
socket.io support out of the box.
Just an off-topic question now: how about mongodb? Any idea how could
I get one instance for each website?
If I run one instance per site my t1.micro box
@alan Why you want to do that? You also normally don't run several MySQL
instances for each site? That's why you can define databases and
collections and not just only collections ;)
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Post
@akira, I had experience with nginx and other languages, but this is
the first time that I had deployed a 100% javascript stack.
Let's wait and see what this stack it's capable of.
A good point for node-http-proxy is the support for socket.io out of the box ;)
--
Att,
Alan Hoffmeister
2012/4/1
Another reason people use node-http-proxy is that it's actually javascript,
which means that one can configure it however they like as they're working
in a true turing complete language. If you want to store your rules in
redis and have a dashboard to change them on the fly, there's nothing
stoppin
I'm actually using mongodb to store those rules, as simple as pie.
--
Att,
Alan Hoffmeister
2012/4/13 Chris Rhoden :
> Another reason people use node-http-proxy is that it's actually javascript,
> which means that one can configure it however they like as they're working
> in a true turing compl
I can at least answer the first question, which is that it doesn't work
easily if you're using bodyparser in front of it. Using bodyparser in your
apps and http-proxy in front of them, there's no issue.
I am not sure I understand your second question.
On Fri, Apr 13, 2012 at 10:35 AM, akira wrot
On Fri, Apr 13, 2012 at 12:01 PM, akira wrote:
> Ok, so that means I leave the bodyParser middleware config out of the
> node-proxy config?
Yes.
> What I meant by my typical use case is this:
>
> # Vhosts
> apps A1 on port 8001, A2 on port 8002 are load balanced and serves --
> > www.domainA
This is all interesting. My reason for using node-http-proxy is that I have
a fully featured programming language for rules in my proxy. It lets me
rewrite in a very natural way, and inspect requests very deeply before
determining which app to forward to.
If you are digging nginx, then keep at it.
24 matches
Mail list logo
