Tom de Bruijn
Tom de Bruijn
Correct, the middleware we depend on now is `ActionDispatch::DebugExceptions`. Same issue exists when removing that middleware. This issue was from before that. As discussed we should add a config option...
Will probably be fixed with https://github.com/appsignal/appsignal-ruby/issues/159 where we will be at the top of the middleware stack so that we don't depend on other middleware to be injected at a...
Suggested using this: ```ruby # config.ru begin require ::File.expand_path('../config/environment', __FILE__) rescue Exception => error Appsignal.send_error(error) raise error end ```
Question: Do we want to support this in the gem itself or just add it to the documentation as an option.
Documented in https://docs.appsignal.com/ruby/integrations/rails.html#error-reporting-during-start-up Leaving open to discuss the option to support it directly in the gem.
Waiting for a Grape app where we can reproduce the original problem with
Related #443
Hi there, it's currently possible to configure AppSignal using Ruby code . Instead of a DSL you are able to pass along a hash to the `Appsignal::Config.new` method. ```ruby Appsignal.config...
Yes, you should call `Appsignal.start` manually, if in a Rails app, in an initializer, so that it overwrites the original config loaded during Rails boot. I understand the advantages, but...
Our integration already calls start logger, it should not be necessary to call it unless you change any logger config options. Since our Railtie already calls it. There should not...