We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
The text was updated successfully, but these errors were encountered:
dvalfre
No branches or pull requests
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.The text was updated successfully, but these errors were encountered: