This repository was archived by the owner on Dec 8, 2020. It is now read-only.
Ensure development always logs to a file #179
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
binarylogic force-pushed the 168-ensure-development-log-writing branch from 9ab169f to f0aea4a Compare 
binarylogic force-pushed the 168-ensure-development-log-writing branch from f0aea4a to 8051878 Compare Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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.
This ensures that the
developmentenvironment always logs to thelog/development.logfile. This is the Rails default and Timber should go with it. In general, we recommend logging development logs to STDOUT only, but it's not our place to change defaults.Closes #168
Closes #146
Closes #123