From af9a14c49cd0e33090765885eb0fa7abefac84ff Mon Sep 17 00:00:00 2001 From: Jacob Vosmaer Date: Thu, 16 Jan 2014 18:40:45 +0100 Subject: [PATCH] Explain that `limit` only applies to the check --- config/gitlab.yml.example | 4 ++-- lib/tasks/gitlab/check.rake | 2 ++ 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/config/gitlab.yml.example b/config/gitlab.yml.example index 71d46d4a1..71cbd07ef 100644 --- a/config/gitlab.yml.example +++ b/config/gitlab.yml.example @@ -116,8 +116,8 @@ production: &base # ========================== ## LDAP settings - # You can inspect the first 100 LDAP users with login access by running: - # bundle exec rake gitlab:ldap:check[100] RAILS_ENV=production + # You can inspect a sample of the LDAP users with login access by running: + # bundle exec rake gitlab:ldap:check RAILS_ENV=production ldap: enabled: false host: '_your_ldap_server' diff --git a/lib/tasks/gitlab/check.rake b/lib/tasks/gitlab/check.rake index 20d5f03d6..461e70ea4 100644 --- a/lib/tasks/gitlab/check.rake +++ b/lib/tasks/gitlab/check.rake @@ -682,6 +682,8 @@ namespace :gitlab do namespace :ldap do task :check, [:limit] => :environment do |t, args| + # Only show up to 100 results because LDAP directories can be very big. + # This setting only affects the `rake gitlab:check` script. args.with_defaults(limit: 100) warn_user_is_not_gitlab start_checking "LDAP" -- 2.11.0