Phusion Passenger supports Unix-like operating systems, and is available as a gem package, as a tarball, or as native Linux packages.<\/span><\/p>\n\n\n\n The Ruby on Rails framework provides a built-in server tool, which can be accessed with the <\/span>‘<\/span><\/i>rails server<\/i><\/b>‘<\/span><\/i> command. The “rails server” is not an application server by itself, but just a small wrapper that launches your application in an application server. This is why people do not use “rails server” in production. They use an application server such as Passenger directly.<\/span><\/p>\n\n\n\n Passenger is an open source web application server. It handles HTTP requests, manages processes and resources, and enables administration, monitoring and problem diagnosis.<\/span><\/p>\n\n\n\n Passenger is very easy to use, makes deploying in production much easier and is scalable.<\/span><\/p>\n\n\n\n When you deploy your web app to production, there are all sorts of components involved. You may have heard of Unicorn, Puma, Nginx, Apache, and Capistrano. Passenger replaces some components while collaborating with other components.<\/span><\/p>\n\n\n\n In a typical production stack, Nginx or Apache is used as the web server, Passenger as an application server, and Capistrano as a release automation tool. Passenger integrates with Nginx or Apache and manages the application and its resources.<\/span><\/p>\n\n\n <\/p>\n\n\n\n Passenger protects your web apps from various malicious attacks like slow client attacks, common HTTP parser exploits, and privilege escalations.<\/span><\/p>\n\n\n\n A tool is only as good as its users are able to wield it. Passenger comes with world-class documentation to allow you to fully leverage its features.<\/span><\/p>\n\n\n\n Passenger was built with high performance and efficiency in mind. With Passenger\u2019s zero-copy architecture, turbocaching and support for multiple concurrency models, you can count on Passenger to get the most out of your hardware.<\/span><\/p>\n\n\n\n Passenger auto-manages your apps\u2019 processes, restarting them and itself if they ever crash. Passenger also keeps resource hogging apps in check, giving your web app maximum uptime.<\/span><\/p>\n\n\n\n Passenger was battle-tested with some of the most demanding web apps for over a decade. This makes it one of the toughest app servers to date, currently powering over 650,000 web apps.<\/span><\/p>\n\n\n\n Deploy your Ruby, Node.js, Meteor and\/or Python apps from one Passenger instance in seconds. You need not fiddle around with multiple app servers and proxies anymore.<\/span><\/p>\n\n\n\n Passenger prints its own logs not only to the terminal but also to a log file. During startup, Passenger tells you what log file is used. This is typically <\/span>log\/passenger.XXXX.log<\/span>.<\/span><\/p>\n\n\n\n There are also the application logs, such as <\/span>log\/development.log<\/span> and <\/span>log\/production.log<\/span>. These logs are completely separate from Passenger’s own logs. If you use Rails, then Passenger will also print your application logs to the terminal, but it will not print them into Passenger’s log file.<\/span><\/p>\n\n\n\n Nginx and Apache are web servers that enable HTTP transaction handling and serve static files. However, they are not Ruby application servers and cannot run Ruby applications directly. That is why Nginx and Apache are used in combination with an application server, such as Passenger.<\/span><\/p>\n\n\n\n Application servers make it possible for Ruby apps to speak HTTP. Ruby apps (and frameworks like Rails) can’t do that by themselves. On the other hand, application servers typically aren’t as good as Nginx and Apache at handling HTTP requests. Nginx and Apache are better at handling HTTP concurrency management, I\/O security, connection timeouts, etc. It is due to this reason that application servers are used in combination with Nginx or Apache in production environments.<\/span><\/p>\n\n\n\n If you require help, contact SupportPRO Server Admin<\/a><\/p>\n\n\n\n Facing issues? <\/p>\n\n\n\n Our technical supportPassenger and “Rails server” <\/b><\/h2>\n\n\n\n
How Passenger fits in the stack<\/b><\/h2>\n\n\n\n
![\"Passenger-](\"https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2018\/09\/stack.png\")
<\/a><\/figure>\n<\/div>\n\n\nSecurity<\/b><\/h3>\n\n\n\n
Documentation<\/b><\/h3>\n\n\n\n
Optimization<\/b><\/h3>\n\n\n\n
Stability<\/b><\/h3>\n\n\n\n
Reliability<\/b><\/h3>\n\n\n\n
Polyglot<\/b><\/h3>\n\n\n\n
Logs<\/b><\/h3>\n\n\n\n
Nginx and Apache<\/b><\/h3>\n\n\n\n
engineers can solve it. <\/p>\n\n\n\n<\/a><\/span>