We use and love Atlassian Stash (<a href="https://www.atlassian.com/software/stash" rel="nofollow">https://www.atlassian.com/software/stash</a>), it's excellent for code reviews. The diff view options and commenting make it easy to create pull requests, get feedback and eventually merge code into the master branch. (Per branch permissions are awesome too.)<p>Long time ago we also assessed GitLab and found it usable but not quite there yet for production use. Though it looks nicer now.
BitNami (I'm a cofounder) provides free installers, VMs and cloud images for GitLab. You can also spin 1h demos. <a href="https://BitNami.com/stack/gitlab" rel="nofollow">https://BitNami.com/stack/gitlab</a>
Ah, finally a proper package! <a href="https://www.gitlab.com/downloads/" rel="nofollow">https://www.gitlab.com/downloads/</a><p>This will make GitLab an easier choice in the future. If you're looking for a lighter choice Gitbucket is really nice: <a href="https://github.com/takezoe/gitbucket" rel="nofollow">https://github.com/takezoe/gitbucket</a>
We've been using Gitlab side by side with Github for the past few months. In general it's a very nice replacement, but one thing I've been fighting with lately is code review capabilities.<p>The problem I've been having is when I go to a commit, in Github I'll be able to see what's changed (the diffs), but in Gitlab I often get "diff too big and not shown for perf reasons" or suchlike. This inability to reliably view diffs makes me wonder how we're going to do code review on projects hosted on Gitlab.<p>Does anyone else have experience with this, or any workarounds?
We just released GitLab 6.8 minutes ago <a href="https://www.gitlab.com/2014/04/22/gitlab-6-dot-8-released/" rel="nofollow">https://www.gitlab.com/2014/04/22/gitlab-6-dot-8-released/</a> The main new feature of this release is protection against force pushes. Other changes include improvements to mentioning in comments, Merge Request UI improvements and new API features.
I am working on a Brazilian public sector project, and since we only use open source alternatives running on our own servers (for security reasons), we chose Gitlab. It works nicely. The earlier versions consumed a lot of memory, but recently that's getting better. Would not recommend a too lightweight server, though.
Kind of surprised no one has mentioned gogs, which aims to be an on-premise github, but written in golang with a single binary deployment:<p><a href="https://github.com/gogits/gogs" rel="nofollow">https://github.com/gogits/gogs</a>
My previous experience with Gitlab (and others) led me to Gitblit: <a href="http://gitblit.org/" rel="nofollow">http://gitblit.org/</a><p>Gitblit is in another universe in terms of ease of installation, upgrade and maintenance, and very close on features. Even with a .deb package for Gitlab, my upgrade experience with previous versions wouldn't make me leave Gitblit. It's just dead simple.
We've been using GitLab for our production projects for almost a year now.<p>The biggest reason for moving from GitHub to GitLab was not having to worry about additional cost for creating new projects (we have hundreds of projects and most of them are rarely accessed long after they were created).<p>It's also neat that we have the ability to customize GitLab if we wanted to, e.g. in 2012 we ran some experiments to create projects from templates directly in the GitLab interface [1]<p>And lastly, since we're not in an environment with six-digit numbers of users and constant DDOS attacks - we're able to keep a much better uptime than we had before with GitHub.<p>[1] <a href="http://enga.ge/development/creating-a-sturdy-deployment-workflow-using-git/" rel="nofollow">http://enga.ge/development/creating-a-sturdy-deployment-work...</a>
We have gitlab set up at work for our small team, but we never use it. We just do regular old git operations from the CLI and use e-mail and Bugzilla for issue tracking. I've wondered if maybe there was a feature of Gitlab we're not using that we should, but so far nothing's stuck.
When we migrated over from CVS to git, we installed an instance of GitLab. It is really awesome, a private GitHub for your needs. The setup was a pain though, even after following the instructions. Nice to know they have a single installable package now at <a href="https://www.gitlab.com/downloads/" rel="nofollow">https://www.gitlab.com/downloads/</a>.<p>We also use Atlassian Stash and JIRA for a client project (the client migrated from CVS to git) and honestly, found it to be quite similar in functionality and not too much better for the extra costs. Mostly, it helps that both (Stash and JIRA) are linked together, but I'm sure that can be done with GitLab and another issue tracking software like Bugzilla.
I just got my install of Gitlab working last night. I used the omnibus package (bundles its own nginx, ruby, postgresql, etc). I had to tweak the omnibus settings out of the box because unicorn was timing out on the initial page load.<p>After I fixed that, I disabled the bundled nginx so I could instead use the system's nginx. I had to modify the chef configuration scripts to change directory permissions so the www-data nginx could read the git-owned socket.<p>I'm very happy now that I got it working! My only nitpick (aside from some installation frustrations) is that the syntax highlighting for large files can be very slow. Does anyone have any tips for that?
If you like GitLab, checkout GitHost (<a href="https://githost.io" rel="nofollow">https://githost.io</a>) We provide hosted private GitLab instances. We handle upgrades, security fixes, and backups automatically.
A nice feature is that it also features a REST API: <a href="http://doc.gitlab.com/ce/api/" rel="nofollow">http://doc.gitlab.com/ce/api/</a><p>One thing I’m curious about is performance, as with a personal project I found the `grit` git-ruby bindings rather sluggish when loading in multiple repos… The new `rugged` bindings are supposed to perform much better and if I understand in time Gitlab will switch to them.
An open source alternative for Mercurial and hg repositories is RhodeCode [1]. Source code at [2], this is RhodeCode running their own software. It's a nice solution for those who prefer Hg.<p>[1] <a href="https://rhodecode.com/" rel="nofollow">https://rhodecode.com/</a><p>[2] <a href="https://code.rhodecode.com/rhodecode/files/tip/" rel="nofollow">https://code.rhodecode.com/rhodecode/files/tip/</a>
We're using GitLab for source code and issue management, as well as for internal documentation, and I must say it's really great piece of software. Plus, it's very actively developed and gets new features/fixes all the time.
We use GitLab where I work. I was finally able to set it up a few months ago and we've been using it quite heavily since.<p>Whilst we like using it, the UI doesn't always feel intuitive and has changed a lot over the last few versions, 6.8.0 feels worse to us — mainly due to the weird Merge Request UI changes. <a href="https://github.com/gitlabhq/gitlabhq/issues/6842" rel="nofollow">https://github.com/gitlabhq/gitlabhq/issues/6842</a><p>Still, I personally prefer the look and feel of GitHub. But it's a good free solution and we're really grateful for the work people put into it.
For solo work as a dev surrounded by hardware people, I set up GitLab. Installation took a lot of effort and had a surprising number of service dependencies. For a single user it wasn't worth my time to install or maintain. Though, it is a really nice product once running.<p>I switched to Gitweb and sd (<a href="http://syncwith.us/sd/using/" rel="nofollow">http://syncwith.us/sd/using/</a>). I don't love sd, but the overhead of managing source and tickets for myself makes the combo worth it.
At my work, we aren't using gitlab, but looked into it for our own hosted git and it's pretty nice, considering you can do properly managed repos. We do currently use phabricator though for source-code review, which is pretty nice. You can also introduce new code into the system through it using their arc tool. I think a mixture between gitlab & phabricator is pretty nice. Using phabricator for new feature buildout & gitlab for bug tracking would be the ultimate setup for me.
We switched from github + Gitolite to gitlab a few months back and we're loving it. We've had no issues with it and it's really been a great move for us.
At my current job we didn't have any kind of version control for our source,(not even a sharepoint to dump things into).I spent some time trying out a whole bunch of different intalls and finally settled on Gitlab. It's pretty nice and I was able to get it up and running relatively quick once I put it in it's own instance rather than sharing a postgres install with something else.
My organization has been using Gitlab for a while now. We had a few issues earlier with integrating LDAP authentication and sorting out attachments for the wall, but the latest version does seem to fix most issues.
I am still not very happy with the wiki though (doesn't support folders, no way to upload images, doesn't look very good)
Our company has been using Gitlab since Dec 2012, we had a small team and small code base back then. While searching for a good inhouse github replacement I found GitLab had what I wanted and was worth the time effort. It has been nice to see the evolution and all the features available now.
It's cool, and this is a nearly useless comment, but the logo looks to much like an alien out of a Whitley Strieber "non-fiction" story. A little creepy I'm saying. Gitlab needs some branding design love.
I was thinking what GNU could be if they launched GitLab or some alternative to replace the archaic Savannah. It could take the project to a whole new level.
I run a local gitlab appliance (provided by Bitnami) in VMWare on my dev box, so I can easily browse various source code I have, using their web gui.<p>Big fan of it.