Hi all, this might end up being quite the clusterf*ck post, but here it goes. I'm a student sysadmin and have taken on a broken GitLab installation (to be exact, TWO broken Gitlab installations) to fix.
Layout: In a land far far away, there was a git server, and it ran GitLab 5.x. A sysadmin quit, another came on board, and the new sysadmin then abandoned that installation and installed gitlab 6.5.1 / gitlab-shell 1.8 / API v3, which is currently "running." Now, gitlab is in my lap and I am having quite a few problems with it. It's luckily not a production environment yet. I'm a ruby/rails/rake/bundle/gem (?!) noob, so bear with me please :) 1) omniauth-kerberos and the CSRF token authenticity (see https://github.com/gitlabhq/gitlab-public-wiki/wiki/Trouble-Shooting-Guide in the CSRF entry). The omniauth-kerberos thing does not seem to care about that token at all (looking at its HTML, it's just not included), so I went the "bad" way and fixed it using this: http://eric.van-der-vlist.com/blog/2013/11/23/how-to-customize-gitlab-to-support-openid-authentication/ Effectively, I disabled that CSRF token authenticity check. Not a nice way of solving it, but it works for now. It's not something I'd like to have in a production environment though. Does anyone have better ideas? I would not be opposed to learning some Ruby to fix the omniauth module, if that's where the problem lies, but can someone point me in the right direction there? 2) Gitlab <-> Gitlab-shell. It seems something is funky with the interactions there: Neither authorized_keys nor repositories are "syncing": the keys aren't syncing (I have to run that gitlab:setup rake every time) and the repos aren't being created. Funny enough, the wiki repo ([name].wiki.git) is created in the right directory, and shows up in the gitlab-shell log, but the normal repo does not. Running one of those rake-checks that are everywhere in the documentation, I get "can't create, repository is empty". A few notes: - gitlab.yml has the correct path for gitlab_shell - both gitlab.yml and gitlab-shell/config.yml have the correct repos_path (/home/git/repositories) - gitlab-shell/config.yml has the correct authorized_keys file - When I add an SSH key in the gitlab web interface, nothing shows up in the gitlab-shell.log (info log level) - Adding a project yields the following in the logs: I, [2014-02-17T16:23:34.283731 #9166] INFO -- : Adding project ckoch/school.wiki.git at </home/git/repositories/ckoch/school.wiki.git>. But _nothing_ else. No mention of school.git. - The repositories directory of course has the correct permissions, otherwise how would school.wiki.git be created (yes, I checked it, too) gitlab:check output: https://clbin.com/0tNvO Any ideas? Thank you all! Chris -- 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.
