You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
I am using david alongside puma to provide a CoAP + HTTP API with Rails 5.2.
While running puma, I noticed that the coap.only option inside my application.rb is ignored on server startup and important middleware classes like Rack::MethodOverride and ActionDispatch::ShowExceptions get removed. That is because in david's default config coap.only is set to true and the options set in application.rb are not yet evaluated at the time the HTTP middleware gets removed.
For everyone who experiences the same issue, I solved this by patching david's default config by placing
I am using david alongside puma to provide a CoAP + HTTP API with Rails 5.2.
While running puma, I noticed that the
coap.only
option inside myapplication.rb
is ignored on server startup and important middleware classes likeRack::MethodOverride
andActionDispatch::ShowExceptions
get removed. That is because in david's default configcoap.only
is set totrue
and the options set inapplication.rb
are not yet evaluated at the time the HTTP middleware gets removed.For everyone who experiences the same issue, I solved this by patching david's default config by placing
before the
Bundler.require(*Rails.groups)
line in myapplication.rb
.Cheers,
Alex
The text was updated successfully, but these errors were encountered: