-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nginx #208
Comments
Serving web traffic is not something that pm2 covers in terms of features. This project is a process manager for Node.js applications. You're looking for something like this: http://blog.argteam.com/coding/hardening-node-js-for-production-part-2-using-nginx-to-avoid-node-js-load/ |
There are no issues with websockets, at least none that I know of. It has nothing to do with pm2. Nginx has it's benefits, for example it serves static files real fast. But you should think for yourself, try both things and look how it turns out. I think it would be a good idea to avoid nginx at the beginning and keep in mind its features. If at some point you feel that nginx can fit in there, just add it later.
node.js mailing list will work just fine for this particular question |
No, it's actually some kind of nginx config problem. Nginx forums might be a better place to ask, just asked in case people have had similar issues or any experience using nginx and websockets. So I will just run pm2 alone and upgrade to using a nginx proxy if needed. |
I could not find any info on this: When using pm2, does it make sense to use nginx to proxy requests? What might be benefits? I know about faster serving of static files, but are there any more? A negative aspect I found is that even having set the headers there seem to be problems with websockets.
(Yep, this is not an issue .. but there's not even a twitter account to ask)
The text was updated successfully, but these errors were encountered: