> Hi, any ideas anyone why a gem wouldn't be found even if I can use it?
I had a similar problem a while back. I'd upgraded from ruby 1.8.6 to 1.8.7 and the default installation path changed from /usr/bin to /usr/local/bin. I upgraded rubygems at the same time and reinstalled all my gems, so I had two complete versions of both ruby and rubygems on my system. After the upgrade things got strange. When I ran any of my ruby scripts from the console they worked perfectly, but when I ran them from the rails app it couldn't find a couple of recently-installed gems. It finally dawned upon me that it was a difference in paths: I was running the console as user 'root', but the rails app was being run under a mongrel cluster as user 'mongrel'. I set a global path to ruby for all users in /etc/profile and restarted the mongrels, and suddenly the rails app started working ;-) On Nov 6, 2:41 am, Pod Caster <[EMAIL PROTECTED]> wrote: > Hi, any ideas anyone why a gem wouldn't be found even if I can use it? > And it would break the rake command? > > I guess it is some configuration but I can't get it to work. > > Cheers. > -- > Posted viahttp://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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
