gitlab-recipes

Someone wrote a very nice and detailed guide, however upgrading isn't mentioned[0] it also suggests operating under bad practices like running gitlab from /home/ I guess I could write a decent salt-formula to do all this, but I can't handle upgrading of gitlab easily, it always breaks when I take a new branch from git and run a gitlab-ctl reconfigure. [0]: https://github.com/gitlabhq/gitlab-recipes/blob/master/insta...

Reasonably easy: https://github.com/gitlabhq/gitlab-recipes/blob/master/impor...

Hi andmarios, GitLab co-founder here. Thanks for commenting and informing people. For those interested a bit of background. Replacing gitolite with gitlab-shell in GitLab 5.0 was a painful step that we did not take lightly. It enabled GitLab to perform much better (100x faster on some operations) in larger installations (1000+ repo's). It also greatly reduced the moving parts and installation problems people experienced. We tested Puma on GitLab cloud for weeks to see if there where issues but after the switch we ran into big problems so we had to go back to unicorn. The other transitions have similar stories. We try to be careful but we want to end up with a great solution so sometimes we have to make hard choices. I'm sorry we don't have the resourced to provide official support for Gentoo, everything we have is in the user contributed

You are right about Python still being required. I guess it is needed for syntax highlighting http://pygments.org/ I would recommend against using the Vagrant image for production, it is meant for development. For production you can use a CentOS cookbook https://github.com/atomic-penguin/cookbook-gitlab or an Ubuntu script https://github.com/gitlabhq/gitlab-recipes/blob/master/insta...

https://github.com/gitlabhq/gitlab-recipes/blob/master/insta... might help

An up-to-date install script for Ubuntu can be found here: https://github.com/gitlabhq/gitlab-recipes/blob/master/insta...