DEV: Remove logster current context config.

DEV: Remove logster current context config.

Multisite middleware sits at the top of the middleware stack.

diff --git a/config/initializers/100-logster.rb b/config/initializers/100-logster.rb
index 95a3e09..099747a 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"
 

GitHub sha: 82964265

2 Likes

@SamSaffron Can you review this? Thanks!

Yeah… looks good, pretty sure we moved it up the stack a while ago.

Looks like I missed this when I moved the multisite middleware. Thanks for cleaning it up!

3 Likes