Live data from Hacker News

GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

about.gitlab.com

21–30 of 58 posts

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#21
post #19

I've heard some people saying that the recent free private repos from github could potentially hurt or impact gitlab. I'm not entirely sure why since it is free stuff and not things you are paying for. Is there any merit to that or was I just listening to the wrong person? I'm thinking about applying there

I'd imagine the concern is reducing the earliest part of a customer funnel. First they get the free users. GitHub has the network effects and most open source projects using it, so gitlab need to be better in other areas like having free private repos. Then they can upsell these people for features, or be in the mind of someone making a decision on an enterprise license. If the early stage of that funnel is cut off, they lose their chance to get customers to the more profitable parts.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#22
post #10
post #7

How well does on-premises Gitlab work? Can it run relatively maintenance-free? I heard some negative stories, but I don't know what is true. My team of devs doesn't have a dedicated sysadmin.

I'm running GitLab via Docker, and I love it. I previously managed Atlassian instances and I dreaded ever touching the servers. GitLab def has there shit together in this regard. edit: I forgot, when issue, their docker container uses tmp memory that never seems to free itself. I occasionally (once a year) have to rm and recreate the container, which isn't a huge deal for me.

I maintain several Atlassian products in addition to Gitlab on Ubuntu. Definitely agree - we have a whole snapshot / backup databases routine before going near the Atlassian boxes.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#23
post #5

Tangentially related, but GitLab has developed surprisingly good (albeit still incomplete) support for org-mode and many other markup languages. So it's extremely easy to publish say a wiki built with org and they render it beautifully. I've found this invaluable for working solo or in group projects.

I definitely agree, because I use org-mode and gitlab, personally.

However, they are just using the same ruby package that Github uses to render the org-mode to HTML... unfortunately it is far from perfect.

Still, it's MUCH better than the go version in Gogs, so there's that.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#24
post #19

I've heard some people saying that the recent free private repos from github could potentially hurt or impact gitlab. I'm not entirely sure why since it is free stuff and not things you are paying for. Is there any merit to that or was I just listening to the wrong person? I'm thinking about applying there

Maybe, but to me, Gitlab's USP is features they offer that Github doesn't (like CI), not price.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#25
I think Gitlab is awesome. However, their current homepage hides their actual site (the repositories) and makes it hard as a developer to actually get started compared to Github.

Looking through (browsing repositories) there is almost NO adoption to gitlab.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#26

Used GitLab maybe 5 years ago now? I was impressed with it despite its immaturity. These new features look great though. I found the operation of on-prem GitLab to be a bit of a PITA back then, has that changed? There was a whole bunch of rake tasks and junk you needed to run to upgrade and it required a shutdown of the system.

Upgrading is super easy these days when you go with their omnibus installer. That handles all of the upgrade tasks for you, even skipping over versions which was not really possible with the source install days of old.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#27
post #7

How well does on-premises Gitlab work? Can it run relatively maintenance-free? I heard some negative stories, but I don't know what is true. My team of devs doesn't have a dedicated sysadmin.

Why not cloud Gitlab?

There are use cases where on prem is either very attractive or a requirement. We are currently on Github, but there part of me that would really really like to avoid spreading our code all over the Internet (we also use hosted CI) and trusting others. (Yes, Github is probably better at security than me etc ....) However others have very high security requirements where regulations are being violated by being off prem.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#28

I think Gitlab is awesome. However, their current homepage hides their actual site (the repositories) and makes it hard as a developer to actually get started compared to Github. Looking through (browsing repositories) there is almost NO adoption to gitlab.

Well it seems like a very different model to Github.

I don't know the figures, but the teams I encounter using Gitlab are self-hosting, you aren't going to be able to browse their (private) repos.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#29
post #7

How well does on-premises Gitlab work? Can it run relatively maintenance-free? I heard some negative stories, but I don't know what is true. My team of devs doesn't have a dedicated sysadmin.

On-premise runs pretty much maintenance free. I've be running GitLab for ~5 years on-premise with ~200 developers. The issues have all been minimal, and few, over those years.

Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry

#30
post #28

I think Gitlab is awesome. However, their current homepage hides their actual site (the repositories) and makes it hard as a developer to actually get started compared to Github. Looking through (browsing repositories) there is almost NO adoption to gitlab.

Well it seems like a very different model to Github. I don't know the figures, but the teams I encounter using Gitlab are self-hosting, you aren't going to be able to browse their (private) repos.

GitLab is indeed used much more for private repositories than for open source. These are both on self-managed instances and GitLab.com

We used to have a Explore link on our homepage to https://gitlab.com/explore because HN asked for it but it got dropped.

I've asked to reinstate it in https://gitlab.com/gitlab-com/www-gitlab-com/issues/3713

Post reply on HN