No, that wasn't the solution. Simply by ensuring passenger_ruby is correct (exists, is correct, is used by passenger) did not solve this problem for me - at least not on my laptop dev. system. The same setup works on my desktop dev. machine. Same passenger, same rvm, same app, same ruby - one works, the other one doesn't.
Michael Hasenstein wrote: > Michael Hasenstein wrote: >> ME TOO! > > > SOLVED. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-t...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
