> I managed to figure this out. Doh, it was pointing to the wrong
> (nonexistent) version of Passenger.
I was having a crack at automating the passenger version when using
ree the other night, figured out the directory where the latest
version of passenger still, but still have to find a nice solution to
automatically finding the tagged release version of passenger to
Also I noticed in the passenger apache conf when using ree has this:
I think it should point to the ree version of ruby like this:
if anyone knows a reason why PassengerRuby should point to the os
version of ruby and not ree please let me know.
p 07 5656 9696 m 0421 006618