>From >https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md
The use of ruby version managers such as RVM, rbenv or chruby with GitLab in production frequently leads to hard to diagnose problems. Version managers are not supported and we stronly advise everyone to follow the instructions below to use a system ruby. On Mon, Feb 10, 2014 at 3:17 PM, Gervasio Marchand Cassataro <[email protected]> wrote: > When you said "I've compiled v8 (v3.11.8) from source, and installed it (use > v8 guide and checkout 3.11.8)." what did you do after compiling v8? moved > the .a files somewhere in particular? > > Thanks! > > > > On Wednesday, April 10, 2013 6:03:09 AM UTC-3, Srecko Menjic wrote: >> >> I have a problem with same issue, so today I can't offer any advice how to >> fix it. From what I gathered so far bundle refuses to install omniauth gem. >> I've even installed it with command "bundle exec gem install omniauth", but >> with no success. >> >> Anyway, I can offer advice on how to install therubyracer (though I'm >> running ARM platform). The problem lies in libv8 on which therubyracer is >> dependant. >> >> I've compiled v8 (v3.11.8) from source, and installed it (use v8 guide and >> checkout 3.11.8). Modified Gemfile.lock with therubyracer 0.11.4 and libv8 >> 3.11.8.17. >> run >> cd /home/git/gitlab >> sudo -u git -H bundle config build.libv8 --with-system-v8 >> Continue installation normally. >> >> If I find a solution to omiauth I will post. >> >> Cheers. >> >> On Friday, April 5, 2013 1:32:26 PM UTC+2, Jérémie Astori wrote: >>> >>> Hi, >>> >>> Following the official install guide on a Debian Wheezy server, I >>> encounter an error at the section Initialise Database and Activate Advanced >>> Features. >>> >>> When I run the: >>> >>> sudo -u git -H bundle exec rake gitlab:setup RAILS_ENV=production >>> >>> line, I get this: >>> >>> rake aborted! >>> cannot load such file -- omniauth >>> >>> I should mention that I am using Ruby 1.9.3-p392 through the latest RVM. >>> >>> Do you know how I could fix this? >>> >>> Also, I had some issues with therubyracer gem. It was not compatible with >>> my platform, I disabled the corresponding lines in the Gemfile and >>> Gemfile.lock until I find a solution, probably using Node.JS instead of >>> therubyracer. >>> I don't think it has to do with my problems with therubyracer... Right? >>> >>> Thanks in advance! >>> >>> Jérémie >>> >>> PS: Sorry for the double post but I made a mistake setting the object, I >>> preferred to clear things up. > > -- > You received this message because you are subscribed to the Google Groups > "GitLab" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
