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

# frozen_string_literal: true

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

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

warmup do |app|
  client = Rack::MockRequest.new(app)
  client.get('/')
end

map ENV['RAILS_RELATIVE_URL_ROOT'].presence || "/" do
  use Gitlab::Middleware::ReleaseEnv
  run Gitlab::Application
end
Add latest changes from gitlab-org/gitlab@master 2021-02-03 21:09:17 +00:00			`# frozen_string_literal: true`

init commit 2011-10-08 21:36:38 +00:00			`# This file is used by Rack-based servers to start the application.`

Add latest changes from gitlab-org/gitlab@master 2022-04-01 15:08:40 +00:00			`require ::File.expand_path('config/environment', __dir__)`
added RAILS_RELATIVE_URL_ROOT support 2012-12-28 18:11:28 +00:00
Warm up the app so it's fast for the 1st request This would make the application considered ready much slower, but when it's ready, then it's really ready. Before this change, it claims to be ready, but it's annoyingly slow for the first request with GDK. It's 100% 502 for me, for the first request. This shouldn't really affect production or so, because if it's really ready, it should be blazingly fast, and it should not slow things down too much. The culprit here is probably `ActionController::Base.helpers.asset_path` but this could make sure that anything else would load first, too. 2017-12-28 13:55:34 +00:00			`warmup do \|app\|`
			`client = Rack::MockRequest.new(app)`
			`client.get('/')`
			`end`

Add latest changes from gitlab-org/gitlab@master 2021-07-20 09:08:43 +00:00			`map ENV['RAILS_RELATIVE_URL_ROOT'].presence \|\| "/" do`
Release the entire env 2018-02-07 14:44:05 +00:00			`use Gitlab::Middleware::ReleaseEnv`
added RAILS_RELATIVE_URL_ROOT support 2012-12-28 18:11:28 +00:00			`run Gitlab::Application`
			`end`