dblessing

12 ms·

1.
by dblessing 8y ago
Please see Sid's comment at https://news.ycombinator.com/item?id=18443014 . The numbers are from two separate points in time.
2.
by dblessing 8y ago
Sorry for the delay. Due to the spike in imports things are a bit backed up. Your import should be in the queue and will run eventually. As someone else mentioned it can take a lot of time to import, in general, depending on the number of i
3.
by dblessing 8y ago
GitLab.com offers private repos with unlimited users/collaborators for free. You even get 2,000 free CI minutes per month per group.
4.
by dblessing 8y ago
Thanks for your concern. Everything on https://monitor.gitlab.net is for public consumption. We're very transparent :)
5.
by dblessing 8y ago
Sorry about that. Was the 503 on GitLab.com (main application) or on the link in this discussion (monitor.gitlab.net)? The latter is to a public monitoring dashboard. It has been offline a couple of times today due to influx of traffic. We&
6.
by dblessing 8y ago
Sorry about that. We had to scale our monitoring dashboard due to increase in traffic.
7.
by dblessing 8y ago
It went down again for a short time. We're continuing to monitor and adjust resources as needed. We weren't expecting this traffic to our monitoring dashboard, but it's great that so many people are interested in taking a loo
8.
by dblessing 8y ago
I like your idea. However, few performance problems are global. We have a public monitoring dashboard at https://monitor.gitlab.net/ . Embedded in this dashboard are various metrics which will often show a drop in response t
9.
by dblessing 8y ago
Thanks for the kind words. I'm glad you like the swag and enjoy using GitLab.
10.
by dblessing 8y ago
Thanks for your concern :) Many from our team are indeed on high alert.
11.
by dblessing 8y ago
Sorry about that. We had to scale our monitoring dashboard a bit. It's back up at the moment. GitLab.com is separate infrastructure, though, and we hope it remains online despite the added traffic :)
12.
by dblessing 8y ago
Sorry about that. We had to scale our monitoring dashboard a bit. It's back up at the moment.
13.
by dblessing 8y ago
Turnkey is a great way to get GitLab up and running. However, please note that the latest version of Turnkey is based on GitLab version 8.3 ( https://www.turnkeylinux.org/updates/gitlab ) which is nearly 2.5 years old. C
14.
by dblessing 8y ago
Sorry about that. The link from this discussion is to our public monitoring site (separate from GitLab.com). GitLab.com itself it online and the monitoring dashboard is working again, too.
15.
by dblessing 8y ago
Sorry about that. The 502 was only on our public monitoring dashboard for a short time. GitLab.com itself is up and running and the monitoring dashboard is back online now.
16.
by dblessing 8y ago
The Sidekiq memory killer is enabled for both CE and EE by default with the Omnibus package. If you're seeing something different please let us know and we'll see what's going on.
17.
by dblessing 9y ago
Thanks for sharing your experience with GitLab support. I'm happy to follow up on your issue if you reference your ticket number. We absolutely want to help every customer have a good experience. When we fail at that we want to do ever
18.
by dblessing 9y ago
Sorry to hear you're having trouble scaling GitLab. We have many organizations running GitLab and successfully scaling to 10's of thousands of users, and GitLab.com which is the largest GitLab installation. As a GitLab Enterprise
19.
by dblessing 10y ago
> Does this mean if the account has private repositories, even if unused / dormant, that a username cannot be freed? Correct. We understand that sometimes users will be dormant for a while and when they have data of any kind, we hav
20.
by dblessing 10y ago
I'm glad you love using GitLab to manage your automation projects. Luckily, you can still use the Omnibus install but change the default usernames :) In `/etc/gitlab/gitlab.rb` we have the following configuration options
21.
by dblessing 10y ago
Thanks for recognizing our Core Team, too. They're an integral part of our community. :)
22.
by dblessing 10y ago
We are investigating what it will take to enable this on GitHost.io. At first glance, it doesn't seem to be too difficult. I created https://gitlab.com/gitlab-com/githost/issues/12 to track this feature
23.
by dblessing 11y ago
In EE there is a nightly LDAP sync worker that will auto-block any LDAP users that are no longer in the directory. This should address the active user count issue for licensing.
24.
by dblessing 11y ago
This is definitely not normal. For 20 users, 8GB is more than enough and it should not require constant restarts. Please check out https://about.gitlab.com/getting-help . Message me on Freenode #GitLab @ dblessing or Twitter