1. 24 Jan, 2019 1 commit
  2. 04 Jan, 2019 1 commit
  3. 15 Oct, 2018 1 commit
  4. 13 Oct, 2018 1 commit
  5. 10 Oct, 2018 1 commit
    • Zeger-Jan van de Weg's avatar
      Remove Git circuit breaker · 30b4ce94
      Zeger-Jan van de Weg authored
      Was introduced in the time that GitLab still used NFS, which is not
      required anymore in most cases. By removing this, the API it calls will
      return empty responses. This interface has to be removed in the next
      major release, expected to be 12.0.
      30b4ce94
  6. 24 Sep, 2018 1 commit
  7. 21 Sep, 2018 1 commit
  8. 03 Sep, 2018 1 commit
  9. 08 Aug, 2018 1 commit
    • Ævar Arnfjörð Bjarmason's avatar
      Add ability suppress the global "You won't be able [use] SSH" message · b6ba8cc6
      Ævar Arnfjörð Bjarmason authored
      This fixes gitlab-org/gitlab-ce#49953, as noted in the documentation
      this feature is intended to be used when SSH certificates are
      enabled. Then this warning becomes not only pointless, but also
      misleading.
      
      This builds on top of gitlab-org/gitlab-ce!21009 since both need to
      modify the same documentation, which avoids a merge conflict.
      
      See also the gitlab-org/gitlab-ce#49218 issue and associated merge
      request.
      b6ba8cc6
  10. 27 Jul, 2018 3 commits
  11. 11 Jul, 2018 1 commit
  12. 06 Jun, 2018 1 commit
  13. 29 May, 2018 1 commit
  14. 28 May, 2018 1 commit
  15. 04 May, 2018 1 commit
    • Bob Van Landuyt's avatar
      Store application wide terms · 3d6d0a09
      Bob Van Landuyt authored
      This allows admins to define terms in the application settings.
      
      Every time the terms are adjusted, a new version is stored and becomes
      the 'active' version. This allows tracking which specific version was
      accepted by a user.
      3d6d0a09
  16. 04 Jan, 2018 1 commit
  17. 08 Dec, 2017 1 commit
    • Bob Van Landuyt's avatar
      Move the circuitbreaker check out in a separate process · f1ae1e39
      Bob Van Landuyt authored
      Moving the check out of the general requests, makes sure we don't have
      any slowdown in the regular requests.
      
      To keep the process performing this checks small, the check is still
      performed inside a unicorn. But that is called from a process running
      on the same server.
      
      Because the checks are now done outside normal request, we can have a
      simpler failure strategy:
      
      The check is now performed in the background every
      `circuitbreaker_check_interval`. Failures are logged in redis. The
      failures are reset when the check succeeds. Per check we will try
      `circuitbreaker_access_retries` times within
      `circuitbreaker_storage_timeout` seconds.
      
      When the number of failures exceeds
      `circuitbreaker_failure_count_threshold`, we will block access to the
      storage.
      
      After `failure_reset_time` of no checks, we will clear the stored
      failures. This could happen when the process that performs the checks
      is not running.
      f1ae1e39
  18. 23 Nov, 2017 1 commit
  19. 20 Nov, 2017 1 commit
  20. 23 Oct, 2017 1 commit
  21. 17 Oct, 2017 1 commit
  22. 13 Oct, 2017 1 commit
  23. 30 Aug, 2017 2 commits
    • Nick Thomas's avatar
      Rework the permissions model for SSH key restrictions · 68470602
      Nick Thomas authored
      `allowed_key_types` is removed and the `minimum_<type>_bits` fields are
      renamed to `<tech>_key_restriction`. A special sentinel value (`-1`) signifies
      that the key type is disabled.
      
      This also feeds through to the UI - checkboxes per key type are out, inline
      selection of "forbidden" and "allowed" (i.e., no restrictions) are in.
      
      As with the previous model, unknown key types are disallowed, even if the
      underlying ssh daemon happens to support them. The defaults have also been
      changed from the lowest known bit size to "no restriction". So if someone
      does happen to have a 768-bit RSA key, it will continue to work on upgrade, at
      least until the administrator restricts them.
      68470602
    • Nick Thomas's avatar
      Add settings for minimum key strength and allowed key type · b0f982fb
      Nick Thomas authored
      This is an amalgamation of:
      
      * Cory Hinshaw: Initial implementation !5552
      * Rémy Coutable: Updates !9350
      * Nick Thomas: Resolve conflicts and add ED25519 support !13712
      b0f982fb
  24. 27 Jul, 2017 1 commit
  25. 13 Jul, 2017 1 commit
    • Robin Bobbitt's avatar
      Fixes needed when GitLab sign-in is not enabled · 672a68d3
      Robin Bobbitt authored
      When sign-in is disabled:
       - skip password expiration checks
       - prevent password reset requests
       - don’t show Password tab in User Settings
       - don’t allow login with username/password for Git over HTTP requests
       - render 404 on requests to Profiles::PasswordsController
      672a68d3
  26. 10 May, 2017 1 commit
  27. 03 Apr, 2017 1 commit
  28. 07 Mar, 2017 1 commit
  29. 02 Mar, 2017 1 commit
  30. 01 Mar, 2017 1 commit
  31. 06 Feb, 2017 1 commit
  32. 12 Jan, 2017 1 commit
    • Horacio Sanson's avatar
      Add support for PlantUML diagrams in Asciidoc. · f986b4c4
      Horacio Sanson authored
      This MR enables rendering of PlantUML diagrams in Asciidoc documents. To add a
      PlantUML diagram all we need is to include a plantuml block like:
      
      ```
      [plantuml, id="myDiagram", width="100px", height="100px"]
      --
      bob -> alice : ping
      alice -> bob : pong
      --
      ```
      
      The plantuml block is substituted by an HTML img element with *src* pointing to
      an external PlantUML server.
      
      This MR also add a PlantUML integration section to the Administrator -> Settings
      page to configure the PlantUML rendering service and to enable/disable it.
      
      Closes: #17603
      f986b4c4
  33. 29 Dec, 2016 1 commit
  34. 04 Nov, 2016 1 commit
  35. 29 Sep, 2016 1 commit
  36. 19 Aug, 2016 1 commit
  37. 08 Aug, 2016 1 commit