Why do you need nginx with passenger for RoR?

Question

I know that nginx is a web server, and passenger is an app server. We can just run

passenger start

to start up our rails application, and everything seems to work fine. But there are a lot of posts about setting up nginx as a reverse proxy.

It would be helpful if an expert on this broke down each component, and explain why need nginx and passenger together, and the role of each.

Questions for thought:
- What is the main purpose of wrapping the passenger around nginx, as opposed to running passenger standalone?
- Is it bad to just run passenger standalone?
- Does running "passenger start" boot up its own nginx server?

Expansive

Answer 1

All your questions are answered in the official Passenger documentation.

• Why Passenger is needed, and how it relates to Nginx, and how Passenger fits relative to the rest of the stack: Fundamental Concepts
• How Passenger Standalone is different from Passenger for Nginx: Integration modes
• Is it bad to just run passenger standalone? No, as described in Integration modes
• Does running "passenger start" boot up its own nginx server? Yes, by default. Passenger Standalone also has a "builtin" engine that does not boot up an Nginx server, for specialized configurations: https://www.phusionpassenger.com/library/config/nginx/optimization/#switching-to-passenger-standalone-with-the-builtin-http-engine

Unprejudiced

FYI: Hongli is the Co-founder of Phusion, developer of the Passenger application - github.com/FooBarWidget – Brutish

Answer 2

I'm not an expert of web-servers, though I always deploy my Rails apps with Passenger behind Apache/Nginx.

Let me just list several advantages of this approach (there might be more options and reasons for doing it):

1. Passenger is a standalone server. It means, it was designed to run on a single machine. You can't balance working of two passenger servers the way you can with Apache/Nginx.
2. You can run only single application on given machine with Passenger.
3. Static assets management can be done with Nginx, without ever hitting passenger.
4. It's very easy for an attacker to make your site unresponsive by sending too many request. Nginx/Apache gives you ability to block certain IPs.

Defroster

Passenger author here. 1) This is not true, you can load balance things between Passenger instances just fine. Use any standard HTTP load balancer. 2) This is also not true, Passenger is explicitly designed for multitenancy. It is in fact the only Ruby application server with support for multitenancy. 3) Passenger already configures Nginx in such a way that static assets are directly served from Nginx, without hitting Passenger or the app. – Unprejudiced