1. 29 Apr, 2019 1 commit
  2. 04 Apr, 2019 1 commit
  3. 02 Jan, 2019 4 commits
  4. 25 Oct, 2018 3 commits
  5. 22 Oct, 2018 1 commit
  6. 20 Sep, 2018 1 commit
  7. 08 Sep, 2018 1 commit
  8. 06 Sep, 2018 2 commits
  9. 14 Aug, 2018 1 commit
  10. 09 Jul, 2018 1 commit
  11. 11 May, 2018 1 commit
  12. 10 May, 2018 1 commit
  13. 07 Apr, 2018 2 commits
  14. 06 Apr, 2018 1 commit
  15. 05 Apr, 2018 1 commit
  16. 28 Mar, 2018 2 commits
  17. 25 Feb, 2018 1 commit
  18. 22 Feb, 2018 1 commit
  19. 15 Feb, 2018 1 commit
  20. 06 Feb, 2018 9 commits
  21. 08 Dec, 2017 1 commit
  22. 07 Dec, 2017 1 commit
  23. 24 Oct, 2017 1 commit
  24. 06 Oct, 2017 1 commit
    • to1ne's avatar
      Create idea of read-only database · d1366971
      to1ne authored
      In GitLab EE, a GitLab instance can be read-only (e.g. when it's a Geo
      secondary node). But in GitLab CE it also might be useful to have the
      "read-only" idea around. So port it back to GitLab CE.
      
      Also having the principle of read-only in GitLab CE would hopefully
      lead to less errors introduced, doing write operations when there
      aren't allowed for read-only calls.
      
      Closes #37534.
      d1366971