IntenseWebs/discourse
3
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2025-02-25 18:55:32 -06:00
Code Issues Packages Projects Releases Wiki Activity

DEV: Remove logster current context config.

Browse Source 
Multisite middleware sits at the top of the middleware stack.
This commit is contained in:
Guo Xiang Tan 2020-07-01 11:44:00 +08:00
parent ac968f5363
commit 82964265cc
No known key found for this signature in database
GPG Key ID: FBD110179AAC1F20
1 changed files with 0 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
config/initializers/100-logster.rb
View File

@ -83,22 +83,6 @@ end
Logster.store.max_backlog = GlobalSetting.max_logster_logs 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 # TODO logster should be able to do this automatically
Logster.config.subdirectory = "#{GlobalSetting.relative_url_root}/logs" Logster.config.subdirectory = "#{GlobalSetting.relative_url_root}/logs"