This is way out of date now
The information in this post is so out-dated that I wonder why I'm keeping it around. I guess I'm a digital hoarder...
Been using the Omnibus Package of the GitLab Community Edition offered by the AWESOME team behind GitLab and upgrading is a joy now!!
Ignore the rest of this blag-post. It's something past me said. Present me thinks past me is a jerk.
I've been using Gitlab both personally and professionally for a few months now (Since about version 3.0) and only have one gripe and that is I can never seem to upgrade it without breaking something. On my personal server, it's no big deal as I am the only user, but at work...it's a whole other can of worms.
I've only had luck with a minor upgrade. One that pretty much only required a git checkout, pull, and database rake.
Release upgrades (that is, X.0 to X+1.0) there is always some issue encountered that borks the whole thing. I've yet to completely track it down, but I think it may stem from how we have it installed, as we deviate from the defaults a tad.
So now, my upgrade process consists of a fresh install, and a reimport of all the projects. Time consuming to say the least. I'm working on a script to Export existing projects and Import them into the fresh install using API calls, but this only takes care of the project creation in Gitlab. I then have to update my origins for the git projects. (Scripted too eventually)
My advice to anyone wanting to deploy a Gitlab instance (Which I HIGHLY recommend if you use git) is to use Ubuntu Server ,as all the docs are Ubuntu-centric.
--More info when I finish my next upgrade and/or my export/import scripts--