From 82964265cc9467a40ce4e51801862c4b31546c69 Mon Sep 17 00:00:00 2001 From: Guo Xiang Tan Date: Wed, 1 Jul 2020 11:44:00 +0800 Subject: [PATCH] DEV: Remove logster current context config. Multisite middleware sits at the top of the middleware stack. --- config/initializers/100-logster.rb | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/config/initializers/100-logster.rb b/config/initializers/100-logster.rb index 95a3e09e7f2..099747ae82a 100644 --- a/config/initializers/100-logster.rb +++ b/config/initializers/100-logster.rb @@ -83,22 +83,6 @@ end Logster.store.max_backlog = GlobalSetting.max_logster_logs -# middleware that logs errors sits before multisite -# we need to establish a connection so redis connection is good -# and db connection is good -Logster.config.current_context = lambda { |env, &blk| - begin - if Rails.configuration.multisite - request = Rack::Request.new(env) - ActiveRecord::Base.connection_handler.clear_active_connections! - RailsMultisite::ConnectionManagement.establish_connection(host: request['__ws'] || request.host) - end - blk.call - ensure - ActiveRecord::Base.connection_handler.clear_active_connections! - end -} - # TODO logster should be able to do this automatically Logster.config.subdirectory = "#{GlobalSetting.relative_url_root}/logs"