delta/gitlab/gitlab-ce.git/config, branch 22964-git-commit-documentation-article

add configurable email subject suffix

2016-10-03T10:07:28+00:00

Merge branch 'initialize-redis' into 'master'

2016-09-30T12:32:18+00:00


Initialize Redis pool in single-threaded context

See merge request !6613

Initialize Redis pool in single-threaded context

2016-09-30T10:27:43+00:00

This side-steps the need for mutexes and whatnot.

Use `Module#prepend` instead of `alias_method_chain`

2016-09-30T10:08:25+00:00

Merge branch 'master' of dev.gitlab.org:gitlab/gitlabhq

2016-09-29T17:02:59+00:00

Merge branch '22364-rails-cache-connection-pool-sidekiq-servers' into 'master'

2016-09-29T12:12:01+00:00


Use a ConnectionPool for Rails.cache on Sidekiq servers

## What does this MR do?

On Sidekiq server we'll use a connection pool to connect to the redis store used for Rails cache. But now we're sure we're not modifying the configuration used on the lazy create Redis connection inside the connection pools. I've create a PR on [redis-activesupport](https://github.com/pacoguzman/redis-activesupport) too. @jacobvosmaer-gitlab make this easier updating the Gitlab::Redis class !6472

Closes #22364

See merge request !6468

Update warn message for MySQL fix

2016-09-28T23:48:32+00:00

Use a ConnectionPool for Rails.cache on Sidekiq servers

2016-09-28T09:14:07+00:00

It’s important to remember that connections on ConnectionPool are created 
when needed so if modify the objects later to create those connections weird 
things could happen

https://gitlab.com/gitlab-com/infrastructure/issues/464#note_15850653

Add Pipelines for Commit

2016-09-27T21:11:13+00:00

Set a restrictive CORS policy on the API for credentialed requests

2016-09-26T12:05:01+00:00

Cross-origin requests can still be made, as long as the client doesn't
use the Rails session cookie to do so. Existing clients should not
be setting 'withCredentials: true', so this should be fine.