Hacker News Reader

Comment by falcon620 | Hacker News Reader

More like "gah, we're going to have to self-host git, aren't we"?

Gogs/Gitea are my current goto for doing this. I expect one or both of them will get a lot of influx if github gets acquired.

Gitlab will also see upticks, but I suspect it's a lot more than most people need/want to maintain.

Bitbucket Cloud & Bitbucket Pipelines. Serverless CI/CD... as in, no servers for you to self-host.

Or you know... just use gitlab.com...

I don't trust them to be compent at operating a large scale service after their insane meltdown february last year.

https://www.theregister.co.uk/2017/02/01/gitlab_data_loss/

Unrelated to that incident, but I feel their web UI to be extremely slow lately. Working with PRs (or "merge requests" as GitLab calls them) and CI pipeline is a pain, you're looking at 1 second response times.

We're not happy with the merge request speed either. We're close to converting the merge request view to Vue, this should speed it up considerably.

To me it doesn't look like it's a front-end issue. I am mainly complaining about the HTTP response time. It seems extremely slow on both pipelines and merge requests, and Vue ain't gonna fix that I'm afraid.

I don't know if it's an optimisation issue with the software itself, or if it's just GitLab.com being overloaded..

Because we're loading everything in one go the database query time and rails rendering time adds up.

Yea totally, github is much more reliable.

https://blog.github.com/2010-11-15-today-s-outage/

Reply on news.ycombinator.com