1. 07 May, 2018 1 commit
  2. 04 May, 2018 1 commit
    • Bob Van Landuyt's avatar
      Store application wide terms · a95259f3a366
      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.
      a95259f3a366
  3. 13 Apr, 2018 1 commit
  4. 23 Mar, 2018 1 commit
  5. 21 Mar, 2018 2 commits
  6. 28 Feb, 2018 1 commit
  7. 23 Feb, 2018 1 commit
  8. 02 Feb, 2018 1 commit
  9. 31 Jan, 2018 1 commit
  10. 22 Jan, 2018 1 commit
  11. 19 Jan, 2018 1 commit
  12. 08 Jan, 2018 1 commit
    • Michael Kozono's avatar
      Backport option to disable writing to `authorized_keys` file · aa813711a3bd
      Michael Kozono authored
      Originally branch 'mk-toggle-writing-to-auth-keys-1631'
      
      See merge request !2004
      
      Squashed commits:
      Add authorized_keys_enabled to Application Settings
      Ensure default settings are exposed in UI
      Without this change, `authorized_keys_enabled` is unchecked when it is nil, even if it should be checked by default.
      Add “Speed up SSH operations” documentation
      Clarify the reasons for disabling writes
      Add "How to go back" section
      Tweak copy
      Update Application Setting screenshot
      aa813711a3bd
  13. 08 Dec, 2017 1 commit
    • Bob Van Landuyt's avatar
      Move the circuitbreaker check out in a separate process · 0c71778c3046
      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.
      0c71778c3046
  14. 29 Nov, 2017 1 commit
  15. 27 Nov, 2017 1 commit
  16. 23 Nov, 2017 3 commits
  17. 17 Nov, 2017 1 commit
  18. 23 Oct, 2017 1 commit
  19. 17 Oct, 2017 1 commit
  20. 31 Aug, 2017 2 commits
    • Zeger-Jan van de Weg's avatar
      Implement the implied CI/CD config for AutoDevOps · 6427b5d35d8d
      Zeger-Jan van de Weg authored
      Behind an application setting, which defaults to false, this commit
      implements the implied CI/CD config. Which means that in the case we
      can't find the `.gitlab-ci.yml` on the commit we want to start a
      pipeline for, we fall back to an implied configuration.
      
      For now the Bash template has been copied to
      `Auto-Devops.gitlab-ci.yml` so the tests actually work.
      
      Fixes #34777
      6427b5d35d8d
    • Sean McGivern's avatar
      `current_application_settings` belongs on `Gitlab::CurrentSettings` · e1c28a485974
      Sean McGivern authored
      The initializers including this were doing so at the top level, so every object
      loaded after them had a `current_application_settings` method. However, if
      someone had rack-attack enabled (which was loaded before these initializers), it
      would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't
      have that method.
      
      To fix this:
      
      1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need
         `Object.new.current_application_settings` to work.
      2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it
         like that in several places.
      3. Change the initializers to use that new form.
      e1c28a485974
  21. 30 Aug, 2017 2 commits
    • Nick Thomas's avatar
      Rework the permissions model for SSH key restrictions · e61111a36891
      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.
      e61111a36891
    • Nick Thomas's avatar
      Add settings for minimum key strength and allowed key type · 769b454c7135
      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
      769b454c7135
  22. 22 Aug, 2017 1 commit
  23. 11 Aug, 2017 1 commit
  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 · 01877dc4c826
      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
      01877dc4c826
  26. 12 Jul, 2017 1 commit
  27. 05 Jul, 2017 1 commit
  28. 03 Mar, 2017 1 commit
  29. 23 Feb, 2017 1 commit
  30. 21 Nov, 2016 2 commits
  31. 10 Nov, 2016 1 commit
  32. 04 Nov, 2016 1 commit
  33. 07 Oct, 2016 1 commit
    • Nick Thomas's avatar
      Enable CacheMarkdownField for the remaining models · 8084d80dbce5
      Nick Thomas authored
      This commit alters views for the following models to use the markdown cache if
      present:
      
      * AbuseReport
      * Appearance
      * ApplicationSetting
      * BroadcastMessage
      * Group
      * Issue
      * Label
      * MergeRequest
      * Milestone
      * Project
      
      At the same time, calls to `escape_once` have been moved into the `single_line`
      Banzai pipeline, so they can't be missed out by accident and the work is done
      at save, rather than render, time.
      8084d80dbce5
  34. 19 Aug, 2016 1 commit
    • Gokmen Goksel's avatar
      Support integration with Koding (online IDE) · de3a3fd08cbb
      Gokmen Goksel authored
      Koding: #index: landing page for Koding integration
      
      If enabled it will provide a link to open remote Koding instance url
      for now we are also providing the sneak preview video for how
      integration works in detail.
      
      Repository: check whether .koding.yml file exists on repository
      
      Projects: landing page: show Run in IDE (Koding) button if repo has stack file
      
      Projects: MR: show Run in IDE Koding button if repo has stack file on active branch
      
      ProjectHelpers: add_koding_stack: stack generator for provided project
      
      With this helper we will auto-generate the required stack template
      for a given project. For the feature we can request this base template
      from the running Koding instance on integration.
      
      Currently this will provide users to create a t2.nano instance on aws
      and it'll automatically configures the instance for basic requirements.
      
      Projects: empty state and landing page provide shortcuts to create stack
      
      projects_helper: use branch on checkout and provide an entry point
      
      This ${var.koding_queryString_branch} will be replaced with the branch
      provided in query string which will allow us to use same stack template
      for different branches of the same repository.
      
      ref: https://github.com/koding/koding/pull/8597/commits/b8c0e43c4c24bf132670aa8a3cfb0d634acfd09b
      
      projects_helper: provide sha info in query string to use existing vms
      
      With this change we'll be able to query existing vms on Koding side
      based on the commit id that they've created.
      
      ref: https://github.com/koding/koding/pull/8597/commits/1d630fadf31963fa6ccd3bed92e526761a30a343
      
      Integration: Docs: Koding documentation added
      
      Disable /koding route if integration is disabled
      
      Use application settings to enable Koding
      
      Projects_helper: better indentation with strip_heredoc usage
      
      Projects_helper: return koding_url as is if there is no project provided
      
      current_settings: set koding_enabled: false by default
      
      Koding_Controller: to render not_found once integration is disabled
      
      Dashboard_specs: update spec for Koding enabled case
      
      Projects_Helper: make repo dynamic
      
      ref: https://github.com/koding/koding/pull/8597/commits/4d615242f45aaea4c4986be84ecc612b0bb1514c
      
      Updated documentation to have right format
      de3a3fd08cbb