gitlab-org--gitlab-foss/config.ru

# This file is used by Rack-based servers to start the application.

if defined?(Unicorn)
  require 'unicorn'

  if ENV['RAILS_ENV'] == 'production' || ENV['RAILS_ENV'] == 'staging'
    # Unicorn self-process killer
    require 'unicorn/worker_killer'

    # Max memory size (RSS) per worker
    use Unicorn::WorkerKiller::Oom, (200 * (1 << 20)), (250 * (1 << 20))
  end
end

require ::File.expand_path('../config/environment',  __FILE__)

map ENV['RAILS_RELATIVE_URL_ROOT'] || "/" do
  run Gitlab::Application
end
init commit 2011-10-08 17:36:38 -04:00			`# This file is used by Rack-based servers to start the application.`

Check specifically for Unicorn in rack config.ru file 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 2014-01-23 12:24:31 -05:00			`if defined?(Unicorn)`
Fix 'uninitialized constant Unicorn' error 2013-12-22 05:08:43 -05:00			`require 'unicorn'`
Add unicorn-worker-killer with memory check Conflicts: Gemfile.lock 2013-12-18 07:49:09 -05:00
Disable Unicorn::WorkerKiller in non-production environments 2015-05-27 22:56:35 -04:00			`if ENV['RAILS_ENV'] == 'production' \|\| ENV['RAILS_ENV'] == 'staging'`
			`# Unicorn self-process killer`
			`require 'unicorn/worker_killer'`

			`# Max memory size (RSS) per worker`
			`use Unicorn::WorkerKiller::Oom, (200 * (1 << 20)), (250 * (1 << 20))`
			`end`
don't use unicorn worker killer if PhusionPassenger is defined 2013-12-20 11:30:34 -05:00			`end`
Add unicorn-worker-killer with memory check Conflicts: Gemfile.lock 2013-12-18 07:49:09 -05:00
init commit 2011-10-08 17:36:38 -04:00			`require ::File.expand_path('../config/environment', __FILE__)`
added RAILS_RELATIVE_URL_ROOT support 2012-12-28 13:11:28 -05:00
			`map ENV['RAILS_RELATIVE_URL_ROOT'] \|\| "/" do`
			`run Gitlab::Application`
			`end`