Live data from Hacker News

Moving to GitLab: Yes, it's worth it

about.gitlab.com

331–340 of 356 posts

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

#331
post #64

Small nit pick, why DO and not Linode? Faster CPU, more RAM and Bandwidth, cheaper as well.

Not sure why the downvote, the article keeps bagging about saving cost, when Linode would have been a much better fit and cheaper.

This isn't another ads or trolls. It is similar to AWS topic and recommending GCP, or Microsft Azure, all three are classed as similar with different tradeoff. So is Linode and DO. I do not think there are any other VPS provider then are in their class mindset wise.

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

#332
post #188

Earlier quoted context omitted.

The native subversion and mercurial support for the same repos is incredibly attractive. Any idea how it converts them to a shared format in real-time?

@mc42 They use a common layer called "VCS server". Here's how it looks like from the system architecture standpoint: https://docs.rhodecode.com/RhodeCode-Enterprise/admin/system...

Thanks, that's really cool.

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

#333

Earlier quoted context omitted.

It doesn't sound incompetent to me, there will always be false positives on that scale. Did they remove the OP's repo, or simply send them a message? If a legitimate email gets caught in your spam filter, do you switch email providers? Github and their process/humans/scripts don't sound like the incompetent ones in this scenario. I would be more concerned that my livelihood depended on such an over reactionary compan…

You're injecting a lot of assumptions into your narrative. My point is simply: if Github is flagging content based on perceived personal morals (not ever being allowed to use the word "retard," even in legitimate contexts), some choose not to associate their work with them.

And their bots hide "your profile from the public", when you are hit:

https://pbs.twimg.com/media/CpGcXmQXEAAyJU4.jpg:large

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

#335
post #180
post #170

Earlier quoted context omitted.

How has your experience of installing gitlab on freebsd been? Anything in particular that can be improved? I'm pretty sure the gitlab team is open for all kind of improvements. :)

Someone wrote a very nice and detailed guide, however upgrading isn't mentioned[0] it also suggests operating under bad practices like running gitlab from /home/ I guess I could write a decent salt-formula to do all this, but I can't handle upgrading of gitlab easily, it always breaks when I take a new branch from git and run a gitlab-ctl reconfigure. [0]: https://github.com/gitlabhq/gitlab-recipes/blob/master/insta.…

The pkg-message of the Gitlab port has some useful links to more documentation.

https://www.freshports.org/www/gitlab/

https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/in...

https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/up...

https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/up...

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

#336
post #29

How about costs compared to Bitbucket? I appreciate what you guys are doing but I think Github is cashing in on their brand and for a while they had the best UX (they still might! but I no longer care anymore as all the competitors are "good enough" for me) which lets them set a high premium people will pay. However, I think it's unfair to leave out Bitbucket, they have come a long way. The first example of 8 develop…

I find Githubs UI pretty poor.

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

#337
post #315
post #287

Earlier quoted context omitted.

I really don't want this to be a witch hunt (not seeing that here, just wary of pointing out individuals)—this is exactly the type of thing a business should take responsibility for as a whole. This was a process failure, IMHO.

Exactly. The point of my comment was just that automation is no excuse for this kind of thing. For me it's still about the organization, and singling out individuals is about as productive as yelling at customer support on the phone.

I think you guys missed my point. In pointing out one individual, I was pointing to the organization as a whole. Github supports this kind over-sensitive social-activism. Example A: dragnet language-police script. Example B: hiring controversial, social-activists.

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

#338
post #204

Earlier quoted context omitted.

Very interesting! I remember trying your game a few months back, but I didn't have the time to really get into it. I was thinking about making a game in Löve for a while now, but I have never done any automated testing with it. Is there a good tutorial for that? Or do you feel like writing one? ;)

I highly recommend using Löve; the simplicity is very compelling. I wrote a bit about testing on my blog, but it's more about the architecture of how the user-input system meshes with the internal reprogrammability. There's a bit about fuzz testing though: https://technomancy.us/180 Maybe I'll follow it up with a more detailed post specifically about automated testing in Löve since it seems to be not well-understood.

Thanks for the link. More information about testing with Löve (heh, "with Love") would be wonderful, I'm only used to Enterprise Java, I'm afraid.

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

#339
post #114

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.

I couldn't help noticing Gogs is hosted on GitHub... https://github.com/gogits/gogs

GitLab also started out on GitHub didn't it?

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

#340
post #38

Earlier quoted context omitted.

Is there anything we can do from our side? We're very interested in making it easier to integrate with GitLab, but also happy to invest some time into making existing integrations easier to set up. Our hope is that with time, it'll become obvious that when developing an application, you integrate with GitLab as well as with BB and GH.

Maybe create a plugin for Visual Studio, like GitHub does. Also try to work with JetBrains to make their GitHub plugin work with GitLab? The GitHub plugin is available during installation, both with Visual Studio and JetBrains products, which makes it much more convenient to use. Things like creating a gist from code in IntelliJ or PyCharm also work out of the box with github.

We're exploring the VisualStudio option but as Job said we currently don't have the knowledge to make that happen. I've logged an issue for this request https://gitlab.com/gitlab-org/gitlab-ce/issues/20686 you can back it and follow it there.

As for JetBrains, we discussed this option with them - it would help if you create an issue for that on their platform as a user request to surface it. The more demand their users will have for this request the more likely it is to happen.

Post reply on HN