Live data from Hacker News

Moving to GitLab: Yes, it's worth it

about.gitlab.com

41–50 of 356 posts

Re: Moving to GitLab: Yes, it's worth it

#41
post #28

What is the benefit of moving to Gitlab from Bitbucket (or Github) for private repos? Same feature set, Gitlab cost more per user and on top of all you have to run your own server? Am I missing something here?

I'll leave the marketing talk to less biased people here, but do note that: - you can use GitLab.com for free: unlimited public and private repositories, unlimited collaborators, free hosting of your Docker images, free hosting of your static site with any static site generator and free CI / CD - GitLab CE is fully open source (MIT Expat). You can easily install it anywhere you want.

"you can use GitLab.com for free"

It seems like that is the main selling point. However, I think that most of us don't want the extra weight of managing yet another tool. Thus why many of us use GitHub to begin with and not something else...

Re: Moving to GitLab: Yes, it's worth it

#42
post #27

As always, we're happy to answer any questions about GitLab.

Any hope to get improvements on the issue tracker?

We hope to ship Issue boards[1] this months, which will be a mayor improvement! But maybe you could be more specific to what you're missing? We'd love to hear your feedback!

[1] https://gitlab.com/gitlab-org/gitlab-ce/issues/17907

Re: Moving to GitLab: Yes, it's worth it

#43

I've run Gitlab for about a year now and I think it's great. However it is sluggish on a 1GB box and I think you need at least 2GB. Since Linode doubled the RAM on their $10 boxes then you can get it for the same price.

My gitlab-ce instance runs on a vm on an internal hypervisor machine. I just upped the RAM provisioning from 2gb to 4gb, and now it's plenty fast.

One of the benefits of working for a software company that started in the pre-cloud era is a surplus of server boxes, now retrieved from colo racks. :-)

Re: Moving to GitLab: Yes, it's worth it

#44
post #28

What is the benefit of moving to Gitlab from Bitbucket (or Github) for private repos? Same feature set, Gitlab cost more per user and on top of all you have to run your own server? Am I missing something here?

I'll leave the marketing talk to less biased people here, but do note that: - you can use GitLab.com for free: unlimited public and private repositories, unlimited collaborators, free hosting of your Docker images, free hosting of your static site with any static site generator and free CI / CD - GitLab CE is fully open source (MIT Expat). You can easily install it anywhere you want.

Nothing is free in life. You should define free because it's border line a buzz word now.

Re: Moving to GitLab: Yes, it's worth it

#46

As always, we're happy to answer any questions about GitLab.

Any ideas of supporting Mercurial, too?

For Mercurial check out RhodeCode which is also supporting some of unique Mercurial features like largefiles, phases, bookmarks.

Re: Moving to GitLab: Yes, it's worth it

#47

I really liked Gitlab when last I tried it, but in the end I went with https://gogs.io/ instead. For a small-ish team this felt like the most straight forward self-hosted solution. Still missing LFS though, which sucks, but it's being worked on.

We've been using https://rhodecode.com for internal repositories: it is also open source, yet has better interface and out-of-the-box LFS support.

Re: Moving to GitLab: Yes, it's worth it

#49

Gitlab users: How many hours per year do you spend on doing maintenance for your setup? (servers, updating, backups, troubleshooting, etc.)

I'm using paid GitLab hosting via the GitLab-owned GitHost.io, so zero: everytime an update comes out I get two e-mails and that's it.

The pricing is extremely competitive. We are a small shop so the smallest package ($35, recommended for up to 30 active users) is good enough. We started with a self-hosted GitLab via docker and switched to GitHost as soon as it was bought by GitLab.

Re: Moving to GitLab: Yes, it's worth it

#50

Gitlab users: How many hours per year do you spend on doing maintenance for your setup? (servers, updating, backups, troubleshooting, etc.)

If you don't want to maintain GitLab, either CE or EE, but would like to use it, you might want to take a look at GitHost.io

The instance I maintain takes me about 15 minutes a month. Security updates are done automatically so all I've got left to do it 'apt-get install gitlab-ce' once or twice a month and thats it!

Post reply on HN