Make logging to stdout work again with implicit development
env
#12514
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.
PR #11060 disabled logging of
rails server
to stdout in non-development environments. It did so by checking whether-e development
was passed explicitly. However, development environment can also be set using theRAILS_ENV
orRACK_ENV
variables or by not specifying an environment at all. In these cases, logging to stdout was suppressed, too. This means that simply runningrails server
would no longer output anything. This PR fixes the problem and adds further tests.