rbenv-vars VS Phusion Passenger

$ git clone https://github.com/rbenv/rbenv.git ~/.rbenv $ echo 'eval "$(~/.rbenv/bin/rbenv init - bash)"' >> ~/.bashrc $ exec $SHELL $ git clone https://github.com/rbenv/ruby-build.git "$(rbenv root)"/plugins/ruby-build $ git clone https://github.com/rbenv/rbenv-vars.git "$(rbenv root)"/plugins/rbenv-vars $ rbenv install 3.2.0 $ rbenv global 3.2.0 # Test complete install with rbenv-doctor $ curl -fsSL https://github.com/rbenv/rbenv-installer/raw/main/bin/rbenv-doctor | bash $ ruby -v # Shows ruby version number if correctly installed $ gem install bundler # You might be prompted to update some gems, see command below $ gem update --system 3.4.6 # Check if this is recommended after bundler installation $ bundle -v # Shows bundler version number if correctly installed

$ sudo apt update; sudo apt upgrade -y $ sudo apt install rbenv $ rbenv init # Follow instructions: append 'eval "$(rbenv init -)"' to ~/.bashrc $ source ~/.bashrc # or disconnect and reconnect $ mkdir -p "$(rbenv root)"/plugins $ sudo apt install git $ git clone https://github.com/rbenv/ruby-build.git "$(rbenv root)"/plugins/ruby-build $ git clone https://github.com/rbenv/rbenv-vars.git "$(rbenv root)"/plugins/rbenv-vars $ curl -fsSL https://github.com/rbenv/rbenv-installer/raw/main/bin/rbenv-doctor | bash $ rbenv install 3.0.3

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.