BigW Consortium Gitlab

  1. 02 Nov, 2017 1 commit
  2. 06 Oct, 2017 1 commit
    • Create idea of read-only database · d1366971
      Toon Claes 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 gitlab-org/gitlab-ce#37534.
  3. 14 Aug, 2017 1 commit
  4. 24 Jul, 2017 1 commit
  5. 05 Jul, 2017 1 commit
  6. 02 May, 2017 1 commit
  7. 25 Apr, 2017 1 commit
  8. 21 Apr, 2017 2 commits
  9. 23 Feb, 2017 2 commits
  10. 25 Jan, 2017 1 commit
  11. 18 Jan, 2017 1 commit
  12. 07 Oct, 2016 1 commit
    • Add markdown cache columns to the database, but don't use them yet · e94cd6fd
      Nick Thomas authored
      This commit adds a number of _html columns and, with the exception of Note,
      starts updating them whenever the content of their partner fields changes.
      
      Note has a collision with the note_html attr_accessor; that will be fixed later
      
      A background worker for clearing these cache columns is also introduced - use
      `rake cache:clear` to set it off. You can clear the database or Redis caches
      separately by running `rake cache:clear:db` or `rake cache:clear:redis`,
      respectively.