Replies: 1 comment
-
Passenger relies on a Ruby package that provides /usr/bin/ruby because its CLI tools depend on that. Fullstaq Ruby does not provide /usr/bin/ruby and instead relies on either absolute paths or PATH-based activation in the shell, and thus cannot satisfy Passenger's Ruby dependency requirement. At least, not until #6 is implemented. So at the moment you'll have to accept that Passenger installs a non-Fullstaq Ruby dependency. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We're trying to use Fullstaq Ruby on an Ubuntu 20.04 EC2 instance with Passenger and Nginx , the latter two installed via the recommended process from the Passenger website.
The problem we're running into is that the passenger apt package depends on Ruby and apt doesn't recognize the Ruby installs from the Fullstaq repository as valid options to meet that dependency, so we end up with an Ubuntu provided Ruby version installed as well.
We've come "close" by configuring passenger options as :
But passenger still boots using the default OS provided Ruby rather than the specific version we install from the Fullstaq repo. A subset of the installed packages can be found here:
Has anyone found a successfully configuration to make Fullstaq Ruby and Passenger work together? Is there a different approach beyond installing the passenger gem and compiling nginx from source? Our team was surprised to find little if any mention of using Fullstaq Ruby and Passenger together in our internet research. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions