Not 100% sure what the difference is, but they're both WRONG. Adding gem directories like that to the load path will only work for suitably small values of "work". Try the instructions here:
http://blog.juliankamil.com/article/26/installing-your-own-ruby-gems-in-a-shared-hosting-environment to get this set up *correctly*. It might not seem like a big deal at first, but the method recommended by your provider will break if gems depend on other gems in your local repository. --Matt Jones On Apr 19, 3:29 pm, Gavin <ga...@thinkersplayground.com> wrote: > Hey all! > > I've got an app on a shared host at the moment. > > They load ruby gems into a dir onto my space: home/myusername/ruby/ > gems/gems and recommend that you include this path by adding it to the > load_path like so: > > $:.push("home/myusername/ruby/gems/gems") > > My question is - is this the same as adding > > config.load_paths += %w(home/myusername/ruby/gems/gems) > > to the environment.rb file? > > If so - cool! > If not, can anyone explain what the difference is? > > Thanks --~--~---------~--~----~------------~-------~--~----~ 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-talk@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 -~----------~----~----~----~------~----~------~--~---
