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
GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
21–30 of 58 posts
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#22How 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.
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#23Tangentially 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.
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
#24I'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
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#25Looking through (browsing repositories) there is almost NO adoption to gitlab.
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#26Used 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.
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#27How 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?
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#28I 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.
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
#29How 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.
Re: GitLab 11.7 Shipped with Releases, Multi-Level Child Epics, and NPM Registry
#30I 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.
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