| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | use Gitlab::UserSettings directly as a singleton instead of ↵ | Mario de la Ossa | 2018-02-02 | 1 | -4/+2 |
| | | | | | including/extending it | ||||
| * | `current_application_settings` belongs on `Gitlab::CurrentSettings` | Sean McGivern | 2017-08-31 | 1 | -0/+2 |
| | | | | | | | | | | | | | | | | | 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. | ||||
| * | Default Git access protocol to `web` | Patricio Cano | 2016-07-05 | 1 | -2/+2 |
| | | |||||
| * | Rename `enabled_git_access_protocols` to singular. | Patricio Cano | 2016-07-05 | 1 | -2/+2 |
| | | |||||
| * | Clarify protocol access check, and make Git HTTP access call more specific. | Patricio Cano | 2016-07-05 | 1 | -1/+1 |
| | | |||||
| * | Only allow Git Access on the allowed protocol | Patricio Cano | 2016-07-05 | 1 | -0/+13 |
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |