41–50 of 96 posts
Just yesterday our workplace gained an interest in setting up Gitlab- can we still use our existing Gitolite install, or do we now have to migrate to Gitlab-shell? We've been extremely happy with gitolite, and I do not see us moving off of that software.
I don't think it's possible to use Gitolite with GitLab >= 5
Annoyingly there don't seem to be instructions or migrating from 4.2 to 5.0 when using MySQL and Apache. https://github.com/gitlabhq/gitlabhq/wiki/From-4.2-to-5.0
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!
Thank you for the reference. I think attributing the authors is a good idea. I've created https://github.com/gitlabhq/gitlabhq/pull/3303
What do you think? Is it ok to attribute to the full name?
Best regards, Sytse
From the front page of gitlab.org: "A fast, secure and stable solution based on Rails & Gitolite." Gitolite is gone, long live gitolite?
gitlabhq also offer Vagrant/Chef VM recipes to quickly get set up.
I encourage anyone considering a change to their VCS/deployment set up to give it a try!
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?
Earlier quoted context omitted.
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!
Hi Arhorak, Thank you for the reference. I think attributing the authors is a good idea. I've created https://github.com/gitlabhq/gitlabhq/pull/3303 What do you think? Is it ok to attribute to the full name? Best regards, Sytse
in the Padrino project, we usually attribute by (GH) nickname, because thats what most programmers build their identity around. Also, all involved are mentioned. In that case, it would be:
- API: improved return codes and docs. (Xylakant, justahero)
See ours:
https://github.com/padrino/padrino-framework/blob/master/CHA...
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. gitlabhq also…
You probably are aware of GitLab CI that is a simpler alternative for Jenkins but I wanted to mention it just to make sure.
Earlier quoted context omitted.
Hi Arhorak, Thank you for the reference. I think attributing the authors is a good idea. I've created https://github.com/gitlabhq/gitlabhq/pull/3303 What do you think? Is it ok to attribute to the full name? Best regards, Sytse
Hi, in the Padrino project, we usually attribute by (GH) nickname, because thats what most programmers build their identity around. Also, all involved are mentioned. In that case, it would be: - API: improved return codes and docs. (Xylakant, justahero) See ours: https://github.com/padrino/padrino-framework/blob/master/CHA...
About mentioning usernames, I figured it might get a bit confusing when we get public projects on GitLab.com, you would have to guess which platform the username belongs to. What do you think?