Gitlab 5.0 released, Gitolite now gone

So I've been poking around the upgrade instructions for moving to gitlab-shell [1] and I notice you ask the user to do this:<p><pre><code> sudo chsh -s /bin/bash git </code></pre> I don't see it changing to anything else later in the instructions.<p>Isn't that a <i>huge</i> security downgrade from using gitolite? Am I missing something?<p>[1] <a href="https://github.com/gitlabhq/gitlabhq/wiki/From-4.2-to-5.0" rel="nofollow">https://github.com/gitlabhq/gitlabhq/wiki/From-4.2-to-5.0</a>

Last time i was installing gitlab after having the nightmare to install and maintain a gitorious installation and was really depressed that it felt like the same nightmare. Pages of pages of copy&#38;paste instructions, followed by half a dozen issues that needed post-install fixing... no, never again..<p>I ended up installing gitblit and was amazed by the quick installation and features. Unpack&#38;run! I can recommend gitblit to everyone who needs a quick&#38;easy to install Git web frontend..<p>But gitlab definitely looks nicer, probably can do even more.. it has pull requests which are (yet) missing in gitblit.

Sytse Sijbrandij from GitLab.com here. Thank you for submitting this. We hope people like the change. We put a lot of hard working in making GitLab more stable and scaling it. Let us know what you think.

I'd like to thank the developers for this great project. I finally convinced my team to switch over from SVN to git after I showed them Gitlab. (GitHub was never an option due to corporate data security policies. Even for GitHub private repos.)

This is great news as Gitolite was the one thing that prevented me from giving Gitlab a try.<p>What are the minimum requirements for a light Gitlab installation? I can't find any recommendations on the site.<p>The thought of deploying Gitlab on a Linode 512 for $20 a month with virtually unlimited private repositories is very exciting.

There is also <a href="http://rhodecode.org/" rel="nofollow">http://rhodecode.org/</a> which i highly recommend

The speed at which this project is evolving is quite impressive. I find myself looking forward the the 22nd every month with anticipation for the next release! Thank you Gitlab team.

I set up gitlab for some "skunkworks" projects at my day job, and it's been really great. The Gitolite dep never bothered me (the gitlab install is well documented), but seems like a good thing.<p>Thanks for your hard work, guys and gals!

From the front page of gitlab.org: "A fast, secure and stable solution based on Rails &#38; Gitolite."<p>Gitolite is gone, long live gitolite?

I have been using Gitlab since version 3 and have found it a joy to work with and I too look forward to the 22nd every month. We use it in our internal network along with Jenkins for CI and a custom built deployment application. It all works very well with 15 developers and QA personnel. The new gitlab-shell hasn't made any difference whatsoever over gitolite and the update went as smoothly as possible.<p>gitlabhq also offer Vagrant/Chef VM recipes to quickly get set up.<p>I encourage anyone considering a change to their VCS/deployment set up to give it a try!

The move away from Gitolite is great as I know it was the source of many of install and upgrade headaches however the new component they've replaced it with is very very closely coupled to GitLab.<p>This could have been a great chance to create a lightweight alternative to Gitolite for other projects to use too.

Annoyingly there don't seem to be instructions or migrating from 4.2 to 5.0 when using MySQL and Apache.<p><a href="https://github.com/gitlabhq/gitlabhq/wiki/From-4.2-to-5.0" rel="nofollow">https://github.com/gitlabhq/gitlabhq/wiki/From-4.2-to-5.0</a>

I really want to give this a go but would like to have it set up to shadow the state of our repos in Github. Anyone have any experience with doing this?<p>Also, when will the docs be updated to reflect the obviation of gitolite?

I think its hilarious that all the Gitlab development is occurring on Github.

Congratulations, the project looks good. I will keep it in mind. I didn't install sometime ago partially because I was already running a Gitolite instance and wasn't sure it would play nice.<p>Great to see Postgres support, can I ask why MySql is the recommended DB?<p>The install instructions are still quite long but it is really good to see them done properly with a separate non-root user. The suggested Ruby version isn't the latest (even on the 1.9.3 branch) although I'm not sure that matters.

Just yesterday our workplace gained an interest in setting up Gitlab- can we still use our existing Gitolite install, or do we now <i>have</i> to migrate to Gitlab-shell?<p>We've been extremely happy with gitolite, and I do not see us moving off of that software.

Any news on supporting a single gitlab instance fronting several load-balanced git servers as backend? Or do both git repositories and gitlab still have to live on same machine?

I'll look forward to bitnami building an installer for it.

I am running Gitlab on an AWS micro-instance which has memory problems with the previous version. Thanks for working hard and improving performance!

The installation guide link on the homepage that takes you to Git is borked at present?!

HURRAH! Gitlab is an excellent product but Gitolite and Resque were making the baby Jesus cry, ran off with your girlfriend and kicked a kid over on his bicycle.<p>V5: Thanks very much, team Gitlab.

+1