| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Increase Unicorn memory limits to 300-350adjust-unicorn-memory-limits | Yorick Peterse | 2016-01-20 | 1 | -2/+2 |
| | | | | | | | | Using this limit on GitLab.com it appears we're able to reduce response timings by about 620 milliseconds compared to the previous limit. See gitlab-org/gitlab-ce!2421 for more information. | ||||
| * | Use env variables for Unicorn memory limits | Yorick Peterse | 2016-01-20 | 1 | -1/+4 |
| | | | | | | This makes it easier for users to use their own limits based on their server configuration. | ||||
| * | Disable Unicorn::WorkerKiller in non-production environmentsrs-no-killers-in-development | Robert Speicher | 2015-05-27 | 1 | -4/+7 |
| | | |||||
| * | Check specifically for Unicorn in rack config.ru file | Дамјан Георгиевски | 2014-01-23 | 1 | -1/+1 |
| | | | | | | Don't assume that if the Rack server is not Passenger then it must be Unicorn. There are many other Rack servers in the world (uwsgi being one example that people use a lot). The reverse check is much more logical, i.e. check explicitly for Unicorn | ||||
| * | Fix 'uninitialized constant Unicorn' error | dprolife | 2013-12-22 | 1 | -0/+1 |
| | | |||||
| * | don't use unicorn worker killer if PhusionPassenger is defined | James Newton | 2013-12-20 | 1 | -4/+6 |
| | | |||||
| * | Add unicorn-worker-killer with memory check | Jacob Vosmaer | 2013-12-18 | 1 | -0/+6 |
| | | | | | | Conflicts: Gemfile.lock | ||||
| * | added RAILS_RELATIVE_URL_ROOT support | Chris Frohoff | 2012-12-28 | 1 | -1/+4 |
| | | |||||
| * | init commit | gitlabhq | 2011-10-09 | 1 | -0/+4 |
 |
index : delta/gitlab/gitlab-ce.git | |
| gitlab.com: gitlab-org/gitlab-ce.git |
| summaryrefslogtreecommitdiff |