Phusion Passenger VS Thin

Secondly, there is, of course, a bug with Passenger and /var/run/passenger-instreg (I can be found in that thread whining). My preferred fix for this is

While there is a debate on which ones are the best, we will be using Passenger and Nginx, since they are both fast and reliable. You may wish to do your own research and see which one works for you.

In this tutorial we will be deploying a Rails app with Passenger, as the application server, and Nginx, as the web server. Also, the Rails app will use Postgres, so we will be installing that as well.

Here's Puma's implementation, and Here's Passenger's implementation.

server { listen 80; listen [::]:80; server_name YOUR_DOMAIN.ORG; # If you deploy without DNS and SSL, you could leave servername blank like below # server_name _; root /home/deploy/APPNAME/current/public; passenger_enabled on; passenger_app_env production; passenger_env_var RUBYOPT '-r bundler/setup'; # Cf issue: https://github.com/phusion/passenger/issues/2409 # Uncomment if you use ActionCable and/or Turbo Streams # location /cable { # passenger_app_group_name APPNAME_websocket; # passenger_force_max_concurrent_requests_per_process 0; # } # Allow uploads up to 100MB in size client_max_body_size 100m; location ~ ^/assets { expires max; gzip_static on; } }

> passenger start =============== Phusion Passenger Standalone web server started =============== PID file: /home/leon/Git/MasoniteDemo1/passenger.3000.pid Log file: /home/leon/Git/MasoniteDemo1/passenger.3000.log Environment: development Accessible via: http://0.0.0.0:3000/ You can stop Phusion Passenger Standalone by pressing Ctrl-C. Problems? Check https://www.phusionpassenger.com/library/admin/standalone/troubleshooting/ ===============================================================================

PHP is great, but not for all of us. What about running Node.js or Python apps? You might be tempted to use proxy_pass but it won't handle the app startup and crashes for us. Luckily we have a better option: Phusion Passenger.

I have been following all day guides on https://www.phusionpassenger.com/ on how to deploy Rails apps with Apache and Passenger.

This one file contains everything needed for this simplified app to run. Run it with ruby main.rb, which should spin up an instance of the Thin web server (the default web server that comes with Sinatra). Visit localhost:4567 and you'll see the JSON response.

The other major thing you'll run into is performance. WEBrick's HTTP parsing code may look hairy but it is fast. Mongrel was the first Ruby HTTP server to implement it's HTTP parser in C using Ragel, which Thin, Unicorn, and Puma all copied; although there's a bug in the original Mongrel HTTP parser where it does not combine the values duplicate HTTP headers (yes, HTTP Header names can actually be repeated).

Now let's run our application using a different server. We'll use Thin, a small, simple, and fast web server.