21–30 of 91 posts
I always use http://gitolite.com , thats enough. nb: I dont see the point of the graph about numbers of questions on SO. A high level of questions = A lot of problem, no :)?
OP here, just to note - I'm not an employee or affiliated with Gitlab in any way (outside of considering working for them once) -- just a rabid fan. I've been at companies where I've tried (and failed) to convince other developers/higher ups that something like automatically creating an instance of an app based on the feature branch (what Gitlab/others are calling a "review-app"), is the best way to test individual f…
I work with self-hosted Gitlab daily and I’ve never thought the UI was bad or slow. In fact, I think it works pretty well. To the other commenters: Do you have any examples? Also, I’m excited about auto deployment. The less tools one needs to get software shipped, the better.
The navigation is still a bit convoluted, but has gotten better. There are still some issues of nested navigation menus and difficult to find pages. As far as page speed goes it has gotten better and they are actively working on this.
As long as the rate of improvement is as good as it is I see no reason to switch to another solution. Especially seeing how the community edition is free and satisfies basic developer needs.
Gitlab is also the only code repository service which integrates CI jobs and statuses as well as a front-end for a self-hosted docker registry. Absolutely a killer feature!
I really like the core of gitlab. It's a really good git hosting system that is easy to maintain and work with. My self hosted instance has broken only twice in the last 1.5 years and it was always because of an upgrade and it was always easily fixed. But now i have to say i'm afraid gitlab is getting bloated. Why not keep the core product as a seperate thing from things like CI? a simple plugin style system would be…
If you don't want to use the CI, it shouldn't get in your way. We'd love to hear any specific suggestions you might have, since we're always looking to improve. You can open an issue about them in [3] if you want.
[1] - https://about.gitlab.com/handbook/product/i2p-demo/
OP here, just to note - I'm not an employee or affiliated with Gitlab in any way (outside of considering working for them once) -- just a rabid fan. I've been at companies where I've tried (and failed) to convince other developers/higher ups that something like automatically creating an instance of an app based on the feature branch (what Gitlab/others are calling a "review-app"), is the best way to test individual f…
The UI is bad period. 85% navigation on a normal laptop display (1080). There are layers and layers of menus and submenus which could easily be combined and make little sense. And i'm not even someone with a 'design aesthetic'. The 'review-app' pattern is interesting but doesn't scale for more complicated apps. You'd need to create a 'review cluster' for every branch which quickly becomes untenable. It's usually not…
Earlier quoted context omitted.
I work with self-hosted Gitlab daily and I’ve never thought the UI was bad or slow. In fact, I think it works pretty well. To the other commenters: Do you have any examples? Also, I’m excited about auto deployment. The less tools one needs to get software shipped, the better.
To see that the UI design is bad at times, take the design of merge requests and issues for example. On Github you can easily see what happens, comments are surrounded by a black border, the name of the comment author and the date are clearly visible and have a different background color from the comment text. Actions like closing and re-opening are distinctly different from comments and are color coded (green -> re-…
[1] - https://gitlab.com/gitlab-org/gitlab-ce/issues/32794
[2] - https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...
OP here, just to note - I'm not an employee or affiliated with Gitlab in any way (outside of considering working for them once) -- just a rabid fan. I've been at companies where I've tried (and failed) to convince other developers/higher ups that something like automatically creating an instance of an app based on the feature branch (what Gitlab/others are calling a "review-app"), is the best way to test individual f…
Bad-ish? Try horrible. GitHub has raised the bar too high for Gitlab to spout the tired developer rhetoric that UI/UX doesn't matter.
We're working very hard on making it a pleasant and enjoyable experience. We're currently planning a navigation overhaul [1]. You can also check out a list of all current UX issues in [2]. And, any specific feedback is greatly appreciated, you can open an issue about anything at [3].
[1] - https://gitlab.com/gitlab-org/gitlab-ce/issues/32794
[2] - https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...
OP here, just to note - I'm not an employee or affiliated with Gitlab in any way (outside of considering working for them once) -- just a rabid fan. I've been at companies where I've tried (and failed) to convince other developers/higher ups that something like automatically creating an instance of an app based on the feature branch (what Gitlab/others are calling a "review-app"), is the best way to test individual f…
Gitlab's UI is absolutely awful and incredibly slow. Would you say the same for other tools, like email, or your IDE or editor? They literally copied every functionality and UI of GitHub when they started out, and the only difference at the time was that Gitlab was a slower version of Github. I'm glad you can self-host it, and that they're open source, they've got that going. But if GitHub would ever open source thei…
We also like to think that we bring a couple of novel features to the game. You can check out a list of all our features in [4]
[1] - https://gitlab.com/gitlab-org/gitlab-ce/issues/32794
[2] - https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...
Earlier quoted context omitted.
I work with self-hosted Gitlab daily and I’ve never thought the UI was bad or slow. In fact, I think it works pretty well. To the other commenters: Do you have any examples? Also, I’m excited about auto deployment. The less tools one needs to get software shipped, the better.
I've used Gitlab for personal projects on a small homelab server. I ran the VM with about 1GB of Memory and 1 vCPU (a Core i3 if I recall correctly). Loading a page could load almost instantly but most of the time it did load after 2 or 3 seconds. Gitlab does not work well when resources are scarce, it does require a bit of a beefy server to get fast and reactive, atleast in my experience. I've found Gitea/Gogs to be…
For personal and home use Gitea/Gogs is probably a better choice indeed. As you point out it runs with much fewer resources and as an added bonus it runs as a single go binary which simplifies hosting it tremendously. You could literally just download the binary and run "$ ./gitea web". Gitlab is another beast in that respect, especially if you do not opt for their Omnibus install.
Pretty sure both GitHub Enterprise and BitBucket Server are the dominant self-hosted Git solutions.
[1]: http://blog.bitrise.io/2017/01/27/state-of-app-development-i...