Open dvalfre opened 11 months ago
Seems that by default when Passenger starts, it first loads system gems, and then the applications on gems. This behaviour generate issues when the application has a different version of the gems than the ones the system has. The case is similar to the one presented here: https://stackoverflow.com/questions/74409118/passenger-bundler-gems-not-loaded-from-deployed-app
A fix will be to extend the control script that handles Passenger to include the variable GEM_PATH as part of the start-up command.
GEM_PATH
Seems that by default when Passenger starts, it first loads system gems, and then the applications on gems. This behaviour generate issues when the application has a different version of the gems than the ones the system has. The case is similar to the one presented here: https://stackoverflow.com/questions/74409118/passenger-bundler-gems-not-loaded-from-deployed-app
A fix will be to extend the control script that handles Passenger to include the variable
GEM_PATHas part of the start-up command.