Re:Dear open-source maintainers, a letter from GitLab
by arihant on Monday January 18, 2016 @08:41PM
(#10928362)
True. There is no denying that on-prem Gitlab has its uses. Maybe not for me, but I can respect that.
The point I was making in the original comment was that Gitlab has absolutely no options without heavy onboarding that is hosted as well as reliable. I wasn't really undercutting their on-prem, just pointing out that comparisons with Github are heavily misplaced.
Re:Dear open-source maintainers, a letter from GitLab
by jobvandervoort on Monday January 18, 2016 @09:29PM
(#10928533)
As said in other threads above, we are aware of the shortcomings of GitLab.com, but working very hard to resolve these [0].
Setting up your own instance is not hard [1], but we're also offering managed hosted instances on GitHost.io nowadays.
If you're still in the middle, you could use the one-click deploy options from providers such as Digital Ocean, Cloud 66 and AWS images [2].
[0]: https://gitlab.com/gitlab-com/operations/issues/42
Definitely. There's not much you can do with self-hosted GitLab that you can't do with pure git. GitLab just makes it easier, IMO. The main reason my company uses it is to restrict the master branch to certain people - doable with pure git, less effort with GitLab.
There's no reason we couldn't use GitHub for this (wouldn't cost much for a team our size), but my company prefers on-prem whenever practical for various reasons.
Self-hosted GitLab doesn't fit all the same uses as GitHub (I wouldn't use it for personal projects), but when it does fit it's great to have.