Talk:GitLab

push/clone etc broken
caused by the instruction

The authorized_keys file get something like: command="/home/git/gitlab-shell/bin/gitlab-shell 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:

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
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
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)