We are getting a bit afield, but I cry CALUMNY and I call out my esteemed
colleague for attempting to place an unqualified smirch on the good name of
Apache httpd. I don't think there's evidence to establish that Apache's
prefork MPM (the default Multi Processing Model used by default on *nix)
Indeed, I stand corrected. My experience with WebSockets and Apache was
only with Apache 2.2 and it looks like mod_proxy_wstunnel does address the
fundamental issues I experienced with previous versions in proxying
WebSockets. The configuration in Apache does look simple, but the
documentation
Hi all,
I'd like to experiment with node.js on our production server to create a small
calendar app.
I was wondering if it's better to run node.js on the same server with Apache,
or to set it up a separate cloud instance?
I'm not sure if one is better than the other.
Best,
Junior Tidal
I've had success running node and nginx on the same digital ocean droplet
fwiw.
Apparently node and apache need to be run alongside each other on separate
ports. The answers to this question might be useful to your process:
http://stackoverflow.com/questions/14369865/running-node-js-in-apache.
I would take a step back first and ask: Is production really the best place
to experiment? I strongly recommend experimenting somewhere else first. If
you truly are experimenting, and have never worked with node.js before, the
safer of the two options you asked about would be to start by putting
Junior,
Not exactly your question, but there are sometimes reasons to proxy your
node.js app behind another Web server (say to share a domain or subdomain
with other applications or content without using a new public port). Choose
nginx in that case if you can. There are good tutorials for
Thanks Jason and David for you input.
Yes, to clarify I've worked on some node apps on a workstation then push them
onto a production server to see how it works with other things on that server.
However, it seems like the better route is to start up a instance dedicated
just for node apps.
+1 I'd also recommend using a dedicated Node.js server. Putting it behind a
(Apache or nginx) proxy defeats it's power of being able to simultaneously
handle a lot of interactions without flooding the machine with threads.
Also really consider what you want to use Node for. I do not recommend it
Junior, sincerely hope that helped. Seems like you made a good choice.
Jason, thanks for the tip: I did not expect Passenger to ship with an nginx
compiler/installer. (Just starting to experiment myself!) Useful not only
for people who aren't system admins, but for those who don't have root on
