summaryrefslogtreecommitdiff
path: root/config/unicorn.rb.example
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-05-261-144/+0
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-04-091-2/+2
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2021-03-291-1/+1
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-081-0/+5
|
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2019-10-041-1/+1
|
* Run do_master_restart callback on server startJan Provaznik2019-07-011-2/+14
| | | | | | | | | | We want to call master_restart callback on start too - this callback is used for cleaning up prometheus files. It has been added to Omnibus already: https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/3350 So make sure that Unicorn example configs are up-to-date and that the same callback is called for Puma too.
* Add experimental support for Pumaan-multithreadingAndrew Newdigate2018-10-251-29/+8
| | | | | | This allows us (and others) to test drive Puma without it affecting all users. Puma can be enabled by setting the environment variable "EXPERIMENTAL_PUMA" to a non empty value.
* Fix rubocop complaining about unicorn.rbBrett Walker2018-10-121-2/+2
|
* Copy important changes from unicorn.rb.example toLin Jen-Shin2018-07-311-4/+4
| | | | | unicorn.rb.example.development. Also remove unneeded configurations and update the comment accordingly. I think REE was long dead.
* Make rbtrace work under unicornStan Hu2018-07-301-0/+4
| | | | | | The Unicorn master resets any signal handlers and prevents rbtrace from working properly as a result. Move the `require 'rbtrace'` call to the Unicorn `after_fork` block and keep the initializer only for Sidekiq.
* Clean up stale Prometheus metrics in before_exec unicorn hooksh-update-unicorn-rb-exampleStan Hu2018-06-111-0/+11
| | | | | | | | | Issuing a SIGUSR2 to a unicorn involves a dance where new workers are spun up before the old ones are shut down. To ensure Prometheus .db files aren't deleted after the new workers are shut down, we need to clean these files up before the unicorn process is run. Relates to https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/2582
* Update prometheus client gem to fix problems with PID handling followingpawel/prometheus_client_pid_reuse_errorPawel Chojnacki2017-07-271-0/+4
| | | | unicorn forking new workers.
* Fix typos and grammarseongahjo2016-11-141-2/+2
|
* Fix typos and grammarAchilleas Pipinellis2016-02-101-1/+2
| | | | [ci skip]
* Edit configuration files for relative URL supportAchilleas Pipinellis2016-02-091-3/+5
| | | | [ci skip]
* Add a note that changing example configuration files requires changing ↵note_about_omnibus_changesMarin Jankovski2015-06-111-0/+3
| | | | omnibus-gitlab.
* Revert "Increase timeout for Git-over-HTTP requests."Dmitriy Zaporozhets2015-03-191-4/+16
| | | | | | | This reverts commit 516bcabbf42d60db2ac989dce4c7187b2a1e5de9. Conflicts: Gemfile
* Change default number of unicorn workers to three.Marin Jankovski2015-03-131-1/+1
|
* Increase timeout for Git-over-HTTP requests.Douwe Maan2015-03-041-16/+4
|
* memory constrained unicorn workersJob van der Voort2014-12-081-4/+2
|
* advise about unicorn workersJob van der Voort2014-12-081-7/+9
|
* Doc: Unicorn minimum worker_processes is 2Crom (Thibaut CHARLES)2014-10-301-0/+1
| | | | A value of 1 cause http push fail (issue #6978 on GitHub)
* Increase unicorn timeout to 60 secondsDmitriy Zaporozhets2014-09-231-1/+1
|
* Use the default Unicorn socket backlog value: 1024Jacob Vosmaer2014-09-121-3/+4
|
* Describe unicorn timeout value in git over httpDmitriy Zaporozhets2014-06-111-0/+14
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Update warnings about relative url support.Marin Jankovski2014-05-131-8/+2
|
* Merge branch 'master' of https://github.com/gitlabhq/gitlabhqCrom (Thibaut CHARLES)2013-12-091-1/+1
|\ | | | | | | | | | | | | Conflicts: config/application.rb config/gitlab.yml.example config/unicorn.rb.example
| * Add warning back.Sytse Sijbrandij2013-11-291-1/+1
| |
| * Unsupported is unclear.Sytse Sijbrandij2013-11-281-1/+1
| |
* | Fixed comments for running gitlab in a non-root pathCrom (Thibaut CHARLES)2013-11-061-1/+3
|/ | | | | - If you don't edit gitlab-shell/config.yml, you wnon't be able to push via SSH (as described here: http://stackoverflow.com/questions/15746336/gitlab-cant-push-code-to-server) - If you don't re-run sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production, some icons won't be visible
* Updated at the request of @f0kThomas Misilo2013-09-281-1/+7
|
* Added reference to the line "ENV['RAILS_RELATIVE_URL_ROOT'] = "/gitlab"" , ↵Thomas Misilo2013-09-271-0/+3
| | | | as it talked about in the gitlab.yml.example
* Update unicorn.rb.exampleSpencer2013-09-131-1/+1
|
* Merge pull request #4845 from mmoll/unicorn_localhostDmitriy Zaporozhets2013-08-251-1/+1
|\ | | | | bind unicorn listener to 127.0.0.1
| * bind unicorn listener to 127.0.0.1Michael Moll2013-08-221-1/+1
| | | | | | | | otherwise it will listen on 0.0.0.0
* | Fix the `service gitlab restart` commandJacob Vosmaer2013-08-231-13/+13
|/ | | | | | | This commit addresses two related issues: - Sidekiq should shut down completely before we restart it; - If we restart unicorn with USR2 we need to kill the old master and worker processes.
* Fix unicorn init and configDmitriy Zaporozhets2013-07-081-1/+1
|
* Add suppoort of unicorn and fog gemsDmitriy Zaporozhets2013-07-081-0/+102
|
* remove unicorn config since we use puma nowDmitriy Zaporozhets2013-04-191-68/+0
|
* Result of misspellings run.Kevin Lyda2013-03-171-1/+1
| | | | | | | | | Most of these are comments but a few are strings for users. Might be an idea to run this from time to time: https://github.com/lyda/misspell-check It runs mostly clean now.
* remove hardcoded app_dir from unicorn.rb.exampleMike Wyatt2013-01-311-1/+1
|
* added RAILS_RELATIVE_URL_ROOT supportChris Frohoff2012-12-281-0/+4
|
* Update comment in example unicorn configCaley Woods2012-09-191-1/+1
| | | The timeout was changed to 30 and the comment wasn't updated. Also I've seen several reports of this timeout not being long enough for quite a few people. It resulted in me getting a 502 bad gateway from nginx until I upped it. Perhaps could back to the default 60 would be better? I changed mine to 300, running on an AWS micro instance.
* Renamed unicorn.rb.orig to unicorn.rb.example since this seems to be more in ↵Tobias Pfeiffer2012-09-151-0/+64
line with the common used naming in the config directory. Plus seeing *.orig files I think of the leftovers of git merges, which left me puzzled for quite some time.
View Lorry Controller Status