diff options
| author | Toon Claes <toon@iotcl.com> | 2017-09-19 10:44:58 +0300 |
|---|---|---|
| committer | Toon Claes <toon@iotcl.com> | 2017-10-06 23:37:40 +0300 |
| commit | d13669716ab0c31ce9039ae9f7f073e33a4dc40f (patch) | |
| tree | 001bb2e6aa76ea7531c93e469c396f7fdcc408a7 /app/services/users | |
| parent | 2cf5dca8f80cdefeb8932bf80417f52f289668c8 (diff) | |
Create idea of read-only database
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.
Diffstat (limited to 'app/services/users')
| -rw-r--r-- | app/services/users/activity_service.rb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/app/services/users/activity_service.rb b/app/services/users/activity_service.rb index ab532a1fdcf..5803404c3c8 100644 --- a/app/services/users/activity_service.rb +++ b/app/services/users/activity_service.rb @@ -14,7 +14,7 @@ module Users private def record_activity - Gitlab::UserActivities.record(@author.id) + Gitlab::UserActivities.record(@author.id) if Gitlab::Database.read_write? Rails.logger.debug("Recorded activity: #{@activity} for User ID: #{@author.id} (username: #{@author.username})") end |