summaryrefslogtreecommitdiff
path: root/config/initializers
diff options
context:
space:
mode:
authorJacob Vosmaer <contact@jacobvosmaer.nl>2014-04-15 12:11:13 +0200
committerJacob Vosmaer <contact@jacobvosmaer.nl>2014-04-15 15:53:14 +0200
commit8d78662e69a11dc82916793d97aba36dacae1440 (patch)
tree485de34ae849b44d923d5df9f6227e9219f8d116 /config/initializers
parent0d3ba71bcb92218585988ca1b9f863a796d6e168 (diff)
downloadgitlab-ce-8d78662e69a11dc82916793d97aba36dacae1440.tar.gz
Give the Rails cache its own Redis namespace
Before this change, Rails cache data was stored in a global Redis namespace. As a consequence, clearing the Rails cache (`rake cache:clear`) would also delete all Sidekiq queue data and session storage. This change puts all Rails cache data in a `cache:gitlab` namespace, making `rake cache:clear` safe again.
Diffstat (limited to 'config/initializers')
-rw-r--r--config/initializers/session_store.rb2
1 files changed, 1 insertions, 1 deletions
diff --git a/config/initializers/session_store.rb b/config/initializers/session_store.rb
index f80b67a554b..5fe5270236b 100644
--- a/config/initializers/session_store.rb
+++ b/config/initializers/session_store.rb
@@ -2,7 +2,7 @@
Gitlab::Application.config.session_store(
:redis_store, # Using the cookie_store would enable session replay attacks.
- servers: Gitlab::Application.config.cache_store.last, # re-use the Redis config from the Rails cache store
+ servers: Gitlab::Application.config.cache_store[1], # re-use the Redis config from the Rails cache store
key: '_gitlab_session',
secure: Gitlab.config.gitlab.https,
httponly: true,