dblessing
- Karma
- 55
- Created
- February 7, 2016 (10y ago)
- Submissions
- 0
Service Engineer at GitLab, Inc.
[ my public key: https://keybase.io/dblessing; my proof: https://keybase.io/dblessing/sigs/UlhUuaJlaN1a7CTVwCBEh3Z9Z-6L2n6sP9SjUA9uXCo ]
[ my public key: https://keybase.io/dblessing; my proof: https://keybase.io/dblessing/sigs/UlhUuaJlaN1a7CTVwCBEh3Z9Z-6L2n6sP9SjUA9uXCo ]
Please see Sid's comment at https://news.ycombinator.com/item?id=18443014. The numbers are from two separate points in time.
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,…
Thanks for your concern. Everything on https://monitor.gitlab.net is for public consumption. We're very transparent :)
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 :)
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.
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…
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…
Thanks for recognizing our Core Team, too. They're an integral part of our community. :)
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.