Gitlab
gravityonmars.com
gravityonmars.com
The chair of the department loves Git, but couldn't find a decent (open source) web solution that could be hosted on our systems (as in not Github). Gitlab is an amazing solution.
The authors use Github because they want to make it easier for people to contribute to Gitlab.
(NB: I have no involvement with Gitlab.)
The best angle to go with is to download an appliance VPS with Gitlab already installed and fool around with upgrading it from there..
Or at least it was when I tried it last week. Anyone have any success with that?
- 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.
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.
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.
When things "just work", more people uptake it.
Why? Development skills are not the same as Sys Admin Skills.
Github has been great to get people using source code control because it just works, including experienced devs, and new ones.
Still, everyone should be using source code control, no excuses. The only way to build that habit, early, often, for the newest and most experienced dev is to make it non existent to create and manage your repos. git init is fantastic.
What you're describing is akin to saying no one should drive a car if they can't design, improvise, fix, repair, and modify every part in the car themselves. It's just not something everyone spends a ton of time on, nor is it realistic, if I'm understanding you correctly.
There's little interest on my part beyond this on what is and isn't trivial.
The people you're taking about have probably never heard of GitLab. They're surely quite happy with GitHub.
It would be like me going on CraigsList and emailing my neighbor selling his in- pieces old sports car and asking what the hell I'm supposed to do with a car in pieces.
I feel like I keep having this same conversation and it's always about git. People wanting things to be easier does not magically make them so.
Now we're looking to integrate it with Phrabricator (http://www.phabricator.com/) which is a bit of a do-everything-goliath of systems but we hope will enable us to do some formalization of code reviews, security audits, and thus our deployment/release processes. (Ideally we want these cryptographically signed off on.)
Has anyone had good experience integrating GitLab with Phabricator or other external tools? Recommendations? Gotchas?
Basically we're looking to leverage some more of these over time as we find the time to invest in the learning curve, without throwing away our lovely, easy to use, already functional, and far more polished GitLab system.
I run GitLab.com and it would be great to have public repo's