Phusion Passenger VS PM2

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.

There are plenty of ways to accomplish this: Docker, Kubernetes, Pulumis, etc., but I don’t like to add too much complexity. So for a basic app, I like to use PM2, a Node.js process manager with great features, including the ability to run our app in the background.

This project will consist of a single "index.js" file that you can deploy anywhere. I recommend using an Nginx reverse proxy and pm2 to keep the service running.

Your app should be running now. To be able to run the app in the background, I will use pm2. Stop your application using "Ctrl + C" and install pm2

https://www.npmjs.com/package/pm2 I found this package. It looks good and solves my problem, I think.

Usually, you have something that restarts it for you. This is what a "process manager" is for, e.g. https://www.npmjs.com/package/pm2 But in most more advanced systems, this is taken care of for you differently. E.g. lambdas are restarted automatically based on how many instances are needed. If you are in container-land, there's usually a health check endpoint on your server that gets pinged by the container orchestrator, and if there's no response, it will kill and redeploy the container.

Additionally, it provides many more features to manage and visualize the processes. More details on PM2 can be found in their official documentation.