Hacker News Reader

Comment by willejs | Hacker News Reader

Can't wait for someone on here to say: "This is why you should run your own gitlab instance".

The best part of running your own in-house gitlab instance is it is almost guaranteed to have substantially less monitoring than GitHub. Meaning nobody in the company will ever be able to prove it has lower availability than GitHub even though it almost certainly does.

The best part of running your own in-house gitlab instance is fiddling too often with the configuration after updates because something broke again. The gitlab ci runners with docker:dind are a constant pain in the ass.

GitLab employee here, specifically on the Runner team! What kind of problems are you facing with `docker:dind`?

We had a recent problem where jobs were hanging due an update in Docker itself, where things halt when running on single core machines as explained in https://gitlab.com/gitlab-org/gitlab-runner/issues/6697. It's being fixed upstream in https://github.com/moby/moby/issues/40514. In the meantime to prevent you from having problems like this, it's always better to use a specific version of Docker for example `docker:19.03.5-dind`. Like this, you have control over which dind version you use and can upgrade when you have tested it beforehand.

In retrospect, we could have caught this issue earlier and informed our users if we had automated pipelines pulling latest images and testing them out, which we started working on yesterday https://gitlab.com/groups/gitlab-org/-/epics/2674 and we started monitoring dind specifically in https://gitlab.com/gitlab-org/ci-cd/tests/dind-image-tests/

My experience hasn't been anything like this. Countless upgrades, rarely a change to configuration. Any changes that did happen were communicated.

Nor with gitlab-runner (and I even fork it to add stuff), and use docker-in-docker.

On prem software has its place. Whether GitLab or some other alternative.

Nah.

This is why you should run your own gogs/gitea instance.

And Phabricator, the most underrated software in history.

I'd love to use a self-hosted VCS (git or svn) that supports directory-level ACLs && painless code review workflow. Can this be achieved with Phabricator?

I noodled around with Phabricator for a while and it's slick in many ways but extremely clunky in others. For instance, importing a repo that exists in another VCS is done at creation time in Gitlab as part of the flow - it's not a completely different step.

In Phabricator, you create the repo, you turn off its access URLs, add URLs for the repo you're mirroring, set them as a mirror source, and then turn the access URLs back on. This is about a 5-10 minute process per repo and it's all clicking around in a UI.

Have you looked at the rhodecode.com for svn/git?

:) arc is mostly pain but the rest is nice. And the project review stuff is genius.

really mixed feelings with phabricator. it's cool to have the concept of review instead of sending each comment immediately, but the UI still sucks. It's hard to understand which repo the pull request/review we are looking at belongs to for instance.

and it gets all f*cked up if you started a comment and didn't close the input. among many other UI stuff (not sure if the UI has improved or if any of it is configurable btw)

GitHub also has batched reviews by the way.

I've been using gogs from extremely early on and switched to Gitea after the fork. The quality of the software is extremely high and it's quite a breeze to self-host. Highly recommend.

Gitea is amazing. It's exactly what I want and need for a Git server, though I know without CI or 'gists' it's not for everyone. But previously I just had a git server on a barebones Linux server (SSH/cli only). Gitea gave me a decent web front end and easy hooks for mirroring. Overhead for the server isn't THAT much more than bare git. I love gitea!

Or Fossil, much simpler.

Or Pijul, still experimental, but where cherry-picking isn't fundamentally broken and which actually directly works with line patches.

Ah yes, on-prem software: where instead of having an outage and someone has to go fix it, you have an outage and _you_ have to go fix it.

I've never had an outage on my own system that didn't take two seconds to fix because some service just needed restarting.

When you don't have to cater to more than 1 user, there are VASTLY fewer things that can go wrong in a way that takes a long time to fix.

Consider yourself lucky that you've never had a hardware issue.

If you're not prepared to deal with that, use a VPS host. That's what I do.

A curse and a blessing. You can fix it as fast as you want. For github, everyone will stop pushing/merging and you will have to wait for them to fix problems you will never encounter.

GitHub/Microsoft’s status as a defense contractor and vendor to NSA/DoD (MS) and ICE (MS and GH) is why you should self-host your repositories, not their uptime levels.

https://www.vice.com/en_us/article/evjwwp/as-githubs-confere...

https://twitter.com/search?q=%23githubdropice

https://twitter.com/githubbers

Several of their staff have resigned over it, and speakers have pulled out of their conference. Their CEO defended the decision to work with the organization that puts young children in concentration camps.

That’s more than enough for me to delete my repos there. Gitea is an excellent and easy-to-deploy replacement that integrates well with Drone and supports u2f.

1) Most people don't care enough about that to even be bothered by it, never mind change their entire tooling and move large amounts of code out of protest.

2) You are the exact same, it seems, if not worse on account of your hypocrisy? Your GitHub address is still listed in your HN bio, you've been active as recently as yesterday, and you're a pro user, so you _literally_ give GitHub money.

If these issues actually matter to you, delete your account. I'm sure someone would love to scoop up the username "sneak". But don't come here on your high horse shouting about ethics while you actively financially support the organization you're lambasting.

My account is comped, and has been since long before the acquisition. I'd forgotten about the link in my bio, as I put it there a long time ago. It's gone now, thank you for reminding me. :)

I am migrating my repositories off of GitHub this week, which is why I now only have about six remaining there instead of the 60+ that I had for many years. The remaining ones are the ones that need to remain online for services that pull from there; I intend to remove my remaining code from the site very soon, on the order of days. I actually happen to be building my new self-hosting server today, having tested out Gitea and found it a perfect replacement.

My account will remain, to squat my username to prevent impersonation, with a single public repo containing only a README explaining the situation and why use of GitHub is inappropriate.

ha! I was thinking of installing in my personal k8s cluster for the hell of it.

Reply on news.ycombinator.com