4 ms·
If you're looking to poke around and try out Gitlab, it's very nice... but it has a few unsightly snags to install that will turn away 90% of people who just wa
by j45 14y ago
If you're looking to poke around and try out Gitlab, it's very nice... but it has a few unsightly snags to install that will turn away 90% of people who just want to try it out... (including how to guides have the usual open-source vapidly miss obvious steps, requires a specific build of Ruby, etc), the latest version of Gitlab doesn't support certain versions of Ruby, and some required libraries are awaiting updating.
The best angle to go with is to download an appliance VPS with Gitlab already installed and fool around with upgrading it from there..
- mbreese 14y agoThe difficulty in getting it to work with CentOS/RHEL is another problem for me. Focusing on Ubuntu is nice, but we run CentOS on our servers and even trying out the software on that distro is quite difficult. Or at least it was when I tried it last week. Anyone have any success with that?
- bchen 14y agoJust installed Gitlab successfully on RHEL6. Some modifications to the installation steps: - I used RVM to install Ruby 1.9.3. This should be fairly straightforward. - adduser command has a different interface on RHEL, but it shouldn’t be hard to figure out. - I used Apache ProxyPass instead of Nginx. unicorn.rb needed to be updated to listen on a tcp port instead of a socket file. - Supplied init.d script did not work out of box. Some modifications were required. - Redis server was installed from REMI. Let me know where you’re stuck and I can try to help you. I agree that Gitlab is not very easy to install, as there are many complicated steps. The benefits of having a free private GitHub, though, were totally worth it.
- Zaeleus 14y agoHere are my notes for when I tried installing Gitlab on a fresh install of CentOS 6.3 a couple of months ago. It goes up to the point of running `rails server` to get you started, and the rest is like setting up a normal Rails application. https://gist.github.com/4362544 https://gist.github.com/4362544
- sytse 14y agoThere is a Chef Cookbook for CentOS https://github.com/atomic-penguin/cookbook-gitlab https://github.com/atomic-penguin/cookbook-gitlab
- drivebyacct2 14y agoThat's going to turn away 90% of people. Really?
- mbreese 14y agoYes. If something is difficult to install, even to evaluate, then people will not put forth the effort to try it out. Their market is pretty niche: people who like GitHub, but don't want to pay for private repositories or need to host it themselves without paying for GitHub enterprise (or have some other need to host things themselves). So, they need to target developers who may or may not be familiar with sysadmin work. On top of that, their installation requirements are pretty specific, so if you don't have a system (or VM) with those settings, you're pretty much left to your own devices. So, yes... I think 90% might be a reasonable number here. It might be a bit high, but it's in the ballpark.
- dotmanish 14y agoThe market definition has another substantially big segment other than the ones concerned with "pay" - the ones who are paranoid about keeping their repositories outside their company firewall.
- drivebyacct2 14y agoMy point was more that it's not hard to manage ruby versions. Certainly not for someone who plans to run their own gitlab instance. I think there is a very small population who are going to go through with downloading and preparing to self host a mini GitHub and won't Google how to manage Ruby versions... I guess either way it turns into a moot discussion of, are they turning 90% of people away, or are they targetting the 10% since the other 90% don't/won't care or have the ability to maintain an instance.