- 15 Apr, 2014 1 commit
-
-
Jacob Vosmaer authored
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.
-
- 25 Dec, 2013 1 commit
-
-
Marin Jankovski authored
-
- 30 Oct, 2013 1 commit
-
-
vollnhals authored
It was not possible to start Gitlab with a redis server running on another host or port. Every other subsystem that uses redis respects the settings in config/resque.yml. This patch uses the configured url from the cache_store configuration. The cache_store configuration already loads the correct redis url from config/resque.yml. Closes #5406
-
- 11 Oct, 2013 1 commit
-
-
Sytse Sijbrandij authored
-
- 15 Aug, 2013 1 commit
-
-
amouhzi authored
Ref: https://github.com/gitlabhq/gitlabhq/commit/e6159b8725f99af78f446f8d33fa0e52b7780430 Ref: https://github.com/gitlabhq/gitlabhq/pull/3204 Ref: https://github.com/gitlabhq/gitlabhq/issues/1228 Add Rails' variable in application.rb to support relative url This variable is used by assets compilation and other modules. Note that user needs to change application.rb too Restrict session cookie to the relative path if set. Ref: https://github.com/gitlabhq/gitlabhq/commit/2c2f1e31856a4decdae469974f5bea8245316f7e Fix Update attachment_uploader.rb bug with relative URL See: https://github.com/gitlabhq/gitlabhq/commit/161afda3fa4fca58f396e9c3acbd72bc14490ace Fix Wall relative bug with attachement files (javascript)
-
- 26 Sep, 2012 1 commit
-
-
Marin Jankovski authored
-
- 13 Oct, 2011 2 commits
-
-
Dmitriy Zaporozhets authored
-
gitlabhq authored
-
- 08 Oct, 2011 1 commit
-
-
gitlabhq authored
-