Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gitlab was down

status.gitlab.com

Post reply on HN
Print view View original

61–70 of 140 posts

Re: Gitlab was down

#61

Post by PhilKunz »

toopok4k3 wrote: post #52
PhilKunz wrote: post #18

It seems like GitLab should indeed focus on stability now. The feature set is great. But it is all not worth it if it keeps disrupting work on a constant basis by being unstable.

I recommend hosting it yourself, works great and is fast on local network. You can run updates when it's convenient to you, not to others. GitLab is a rare software that enables you to be in control.

I've always been a little cautious of running it myself. When I look at the components involved there are a lot of moving parts. And I don't want to be ever in a position where I can't get things started again. If I'm running on premise I'll switch to gitea with drone ci instead.

Re: Gitlab was down

#63

Post by leipert »

andrelaszlo wrote: post #38
softwarelimits wrote: post #31

Hmmm, just today I wanted to install a new virtual machine with the latest Gitlab release to check if it makes sense to run that inhouse... does anybod know if there is a VM, a vagrant machine, an ISO or a repository online that still can be used? Thanks! Or does exist a mirror on github.com? ;)

If you just want to try it out, the easiest is often Gitlab Development Kit. gem install gitlab-development-kit gdk init cd gitlab-development-kit gdk run I doubt it will work today though; it's probably pulling everything from Gitlab. For Docker, check out https://hub.docker.com/r/gitlab/gitlab-ce I haven't tried it out for myself but it seems popular :)

The GDK installation has changed a bit (just set it up today, you need to run gdk install and gdk start (instead of run) for example). Please also note that it involves installing dependencies on your local machine, like e.g. Ruby / Postgres, etc. Here is the link to the GDK: https://gitlab.com/gitlab-org/gitlab-development-kit

Otherwise I would try the docker container OR just install it with omnibus in a VM: https://about.gitlab.com/install/

Re: Gitlab was down

#64

Post by oefrha »

1337shadow wrote: post #51

Back in the days GitLab made it clear that it aspires to be a software company rather than an infrastructure company. The reason I favor GitLab over GitHub is that I can install it on a dedicated server and have blazing fast performance, which helps development performance on an every day basis. I've been maintaining a bunch of deployments of all sorts (k8s, docker-compose, baremetal) for the last years for several c…

> have blazing fast performance

Sorry, but GitLab has never been blazing fast. The gitlab.com instance is notoriously slow — supposedly improved a lot over the past few years, but still feels pretty sluggish. My self-hosted instance isn’t much better.

In fact, a couple of open source maintainer friends looked into migrating to GitLab when GitHub was acquired by MS; they did not precisely because GitLab was too slow.

Re: Gitlab was down

#66

Post by jlengrand »

I used to be a total Gitlab fanboy. I was going to Sid's meetups back in Utrecht 6 years ago, and he's a model of mine to this time.

I would have done anything to stay on the platform, for at home and the office and setup gitlab instances in two different offices.

Since somewhere last year, I moved back to Github primarily, and I'm sad to hear that my company is likely to make the same choice soon.The only reason is stability, and that's a little sad to me. I really want to love the product, but I need something that just works; not bells and whistles

Re: Gitlab was down

#67

Post by niceworkbuddy »

PhilKunz wrote: post #61
toopok4k3 wrote: post #52

Earlier quoted context omitted.

I recommend hosting it yourself, works great and is fast on local network. You can run updates when it's convenient to you, not to others. GitLab is a rare software that enables you to be in control.

I've always been a little cautious of running it myself. When I look at the components involved there are a lot of moving parts. And I don't want to be ever in a position where I can't get things started again. If I'm running on premise I'll switch to gitea with drone ci instead.

GitLab has virtual machine image, so it's really unobtrusive for your system.

Re: Gitlab was down

#68

Post by ownagefool »

wbl wrote: post #58
ownagefool wrote: post #56

Earlier quoted context omitted.

Replying to myself, because it's now on their status page that a firewall change took down the database. This points to there being: - a lack of process and testing on key networking changes. Aren't they doing CI/CD, automated testing and peer review for this? - A SPOF in the database; why couldn't things connect to a secondary for a read-only mode? Quite a lot of the time, things break for stupid reasons. The main d…

Network devices are generally hostile to advanced automation, and if they had both primary and secondary as the same class of machine then the changes would apply to both.

I believe they're hosting in-cloud, which means it's probably not a device and can be automated. Obviously, public IP addresses will be specific to environments, but that's what PRs should double check.

Re: Gitlab was down

#69

Post by frant-hartm »

Uninen wrote: post #8

We use GitLab at work and I use it for personal projects as well, it has been very slow for several days now and they had downtime yesterday as well. I don't mind the general sluggishness of the system that much (as I love the platform in general) but when you can't get your work (nor hobbies) done because of tools breaking, it gets really annoying really fast.

It's still essentially a git repository, you can work locally and push later.

Yes, the issues, MR, reviews are not available, but honestly I wouldn't want to be in a job where I could not get by without it for several hours.

Post reply on HN