Date: Mon, 3 Aug 2015 10:33:56 +0200 From: Torsten Zuehlsdorff <info@toco-domains.de> To: Steve Wills <swills@FreeBSD.org> Cc: ruby@freebsd.org Subject: Re: [Gitlab] Current Status of the port Message-ID: <55BF2774.1090508@toco-domains.de> In-Reply-To: <55BCF71F.2090407@FreeBSD.org> References: <55BA3B55.5010000@toco-domains.de> <20150730152241.GC82229@mouf.net> <55BA4532.40107@toco-domains.de> <20150731135045.GA49801@mouf.net> <55BB8272.3060900@toco-domains.de> <20150731143935.GC49801@mouf.net> <55BB8B17.7050509@toco-domains.de> <55BCDCE3.1090608@FreeBSD.org> <55BCF71F.2090407@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, >>>>> To setup GitLab follow the quide: >>>>> https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md >>>>> >>>>> >>>>> I've created a basic working configuration for default. You just should >>>>> change the "host" in config/gitlab.yml, if you want to use something >>>>> other than "localhost". The rest should work. But please test carefully, >>>>> i've done many changes in the last months. >> >> I built the packages and installed them in a jail, then followed the >> guide. Setting up redis, the database, config, precompiling assets, etc. >> went fine. When I tried to startup gitlab, I get this in the unicorn log: >> >> I, [2015-07-31T19:00:43.855792 #80415] INFO -- : Refreshing Gem list >> /usr/local/www/gitlab/app/controllers/import/bitbucket_controller.rb:5:in `<class:BitbucketController>': >> uninitialized constant Import::BitbucketController::OAuth (NameError) >> from >> /usr/local/www/gitlab/app/controllers/import/bitbucket_controller.rb:1:in `<top >> (required)>' >> > > After commenting out line 5 of: > > /usr/local/www/gitlab/app/controllers/import/bitbucket_controller.rb > /usr/local/www/gitlab/app/controllers/import/gitlab_controller.rb > > I have gitlab up and running. This may be related to some local patches > I have to ruby and gem. Anyway, I'll keep testing it. So far so good! Okay, i could reproduce this problem. It exists, when the Bitbucket option is not used. This seems a little odd, because no other OAuth Provider makes this error. I will have a look. The error is not in your local patches! Greetings, Torsten
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55BF2774.1090508>