You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been having an issue with Passenger not loading the gemset correctly for Rails applications in RVM 1.25.x. This occurs because I am using a config/setup_load_paths.rb file as recommended here:
Adding MY_RUBY_HOME with the correct value and restarting Passenger fixes the issue. This issue occurs in every version of 1.25.x that I've used, so I don't know when it was introduced. I can confirm that it happens in 1.25.14 (latest release) and is reproducible.
I have been having an issue with Passenger not loading the gemset correctly for Rails applications in RVM 1.25.x. This occurs because I am using a
config/setup_load_paths.rb
file as recommended here:https://rvm.io/deployment/passenger3
The MY_RUBY_HOME variable is not being set in the environment file, so RVM never switches to the correct gemset. In my case, it was missing from:
The content of that file looked like this after I did "rvm install ruby-2.0.0-p353":
Adding MY_RUBY_HOME with the correct value and restarting Passenger fixes the issue. This issue occurs in every version of 1.25.x that I've used, so I don't know when it was introduced. I can confirm that it happens in 1.25.14 (latest release) and is reproducible.
The output of rvm info is:
Btw, I backed the RVM 2.0 Bountysource fundraiser, congratulations on completing it.
The text was updated successfully, but these errors were encountered: