Talk:GitLab

Note
This is a Talk page - please see the documentation about using talk pages. Add newer comments below older ones, sign comments using four tildes (~~~~), and indent successive comments with colons (:). Add new sections at the bottom of the page, under a heading (== ==). Please remember to mark sections as "open for discussion" using {{talk|open}}, so they will show up in the list of open discussions.

push/clone etc broken

Talk status

This discussion is done.

caused by the instruction

root #usermod -s /sbin/nologin git

The authorized_keys file get something like: command="/home/git/gitlab-shell/bin/gitlab-shell key<id>",..., <key> which will fail to execute then. Can someone elaborate? -- Hasufell (talk)

if you use nginx / postgresql it is very possible that i broke your install when migrating out of the 5.0 / gitolite versions to newer stuff. i should really rebuild & document since gitlab 6.3.1 is a security release & update the mysql to run the production lock down command instead of the =mysql-versionnumber stuff since that leaves test users and test databases. 666threesixes666 (talk) 07:32, 8 December 2013 (UTC)

Well, I know how to fix that problem sure. But I still don't like the idea of having full shell access for "gitlab-shell". What does work is to make the shell "/usr/bin/git-shell" and add a symlink:

user $ln -s /home/git/gitlab-shell/bin/gitlab-shell /home/git/git-shell-commands/gitlab-shell

But the "commands=" prefix inside the authorized_keys file always points to the full absolute "/home/git/gitlab-shell/bin/gitlab-shell" and I have to manually fix that for any added key... also I don't know if that will have other side-effects like not deleting obsolete keys or something like that. -- Hasufell (talk) 12:02, 8 December 2013 (UTC)

Error 500

Talk status

This discussion is done.

I often geht error 500 when I quickly click on a big source file. Reloading fixes that. I suspect this is something within the server settings, so it's a performance issue? How to tweak that? -- Hasufell (talk) 12:06, 8 December 2013 (UTC)

try behind varnish if you're using apache 666threesixes666 (talk) 00:46, 9 March 2014 (UTC)

init script

Talk status

This discussion is done.

init script has changed. im investigating gitlab 6.6 but not getting far. most everything uses development environment now instead of production. 666threesixes666 (talk) 00:46, 9 March 2014 (UTC)

6-6 stable runs well, however need development instead of production on entire wiki. mysql command needs -without development directive removed. init script needs new set of notes 666threesixes666 (talk) 01:05, 9 March 2014 (UTC)

Wrong configuration instructions

Talk status

This discussion is done.

The layman section says:

user $layman -a gitlab

And the 5 following commands say that they're executed as regular users. This is plainly wrong. You can't use layman or emerge as a regular user, AFAIK.

Then, there is the gitlab configuration section. It tells us to:

root #cp /etc/gitlabhq-7.14/database.yml.mysql /etc/gitlabhq-7.14/database.yml

root #cp /etc/gitlabhq-7.14/gitlab.yml.example /etc/gitlabhq-7.14/gitlab.yml

root #cp /etc/gitlabhq-7.14/resque.yml.example /etc/gitlabhq-7.14/resque.yml

root #cp /etc/gitlabhq-7.14/unicorn.yml.example /etc/gitlabhq-7.14/unicorn.yml

root #cp /var/lib/gitlab-shell/config.yml.example /var/lib/gitlab-shell/config.yml

This is also wrong. Inside /etc/gitlab-*/ there is a symlink to: /opt/gitlabhq-*/config. The configuration files reside there. It is unclear if your to copy them from there into /etc/gitlab-*/ or just keep them inside the same directory. --Renich (talk) 06:21, 17 November 2016 (UTC)

Hi Renich, feel free to update any commands that are executed as the wrong user. It's just a simple template switch. Let me know if you need any help. Kind regards, --Maffblaster (talk) 17:39, 17 November 2016 (UTC)

OK, did it. But, now, I will fix the copy commands. I figured it out and they should be in /etc/gitlabhq-*/ so the post-config copies them accordingly. Also, I discovered that the ownership of files is wrong. Everything should be owned by the git user. At least /etc/gitlab* and /opt/gitlab*. --Renich (talk) 02:40, 18 November 2016 (UTC)

Good work. I will close this discussion now. Please feel free to update anything that is missing. --Maffblaster (talk) 07:00, 11 January 2017 (UTC)