Use custom logger if configured, fallback to Rails.logger/STDOUT only if not #78
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to docs, you can set custom logger for APNs
But it's overwritten by Rails.logger (and it's cool beacause heroku deploys won't work otherwise, as discussed here #56). The drawback is that you cannot specify custom logger any more. So this patch should add usage of defined one, and fallback to Rails.logger/STDOUT if not.
What do you think?