Live data from Hacker News

Gitlab 5.0 released, Gitolite now gone

blog.gitlab.org

21–30 of 96 posts

Re: Gitlab 5.0 released, Gitolite now gone

#21
post #12

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. This could have been a great chance to create a lightweight alternative to Gitolite for other projects to use too.

Yes, we hope to make installing and upgrading GitLab much easier this way. We wanted to allow other projects to use GitLab-shell too, that is why we made it a separate project https://github.com/gitlabhq/gitlab-shell

I know that but much of the authentication and post receive stuff is hard coded to point at the GitLab API.

If you could abstract this it'd be great.

Re: Gitlab 5.0 released, Gitolite now gone

#22

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? Also, when will the docs be updated to reflect the obviation of gitolite?

The easiest way to shadow the state is to add gitlab as a remote to the repos and possibly automate this with a cronjob.

Important docs on master should be up to date.

Re: Gitlab 5.0 released, Gitolite now gone

#23
post #18
post #5

Earlier quoted context omitted.

We're pragmatic about the development of GitLab. A lot of people want public projects, it is the most popular request for GitLab http://gitlab.uservoice.com/forums/176466-general/suggestion...

Next Amsterdam.rb hackathon we'll get it done :D

Looking forward to that! After the previous hackathon we made many improvements to GitLab Vagrant VM :-)

Re: Gitlab 5.0 released, Gitolite now gone

#24
post #12

Earlier quoted context omitted.

Yes, we hope to make installing and upgrading GitLab much easier this way. We wanted to allow other projects to use GitLab-shell too, that is why we made it a separate project https://github.com/gitlabhq/gitlab-shell

I know that but much of the authentication and post receive stuff is hard coded to point at the GitLab API. If you could abstract this it'd be great.

We are open to proposals and pull requests to do this. It is not very productive to abstract things without a few examples of projects it should be generalized for.

Re: Gitlab 5.0 released, Gitolite now gone

#26
post #13

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.)

Did you consider github enterprise or atlassian stash? I personally think gitlab is preferable, but github and bit bucket offer internal deployments.

Re: Gitlab 5.0 released, Gitolite now gone

#29
post #2

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.

Hi Sytse,

Just for future reference:

Its common courtesy to give attributions next to contributed changes in the changelog. I gladly sponsored development of one of them (API: improved return codes and docs, https://github.com/gitlabhq/gitlabhq/pull/2835) and a short nod to the involved persons would be nice.

Keep up the good work, thank you!

Re: Gitlab 5.0 released, Gitolite now gone

#30
post #13

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.)

have you heard of http://rhodecode.org/ ? It supports both HG and git.
Post reply on HN