Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Make log_level explicit in production.rb template #5863

Merged
merged 1 commit into from

4 participants

@rosenfeld

The 'production' environment name is currently checked for setting up
the default log_level to 'info' but that won't work if the environment
is copied to staging.rb, for instance. Better to have it explicitly set.

Please, take a look at the whole discussion in this thread:

https://groups.google.com/forum/?fromgroups#!topic/rubyonrails-core/sLG7EpAWQfg

@rosenfeld rosenfeld Make log_level explicit in production.rb template
The 'production' environment name is currently checked for setting up
the default log_level to 'info' but that won't work if the environment
is copied to staging.rb, for instance. Better to have it explicitly set.
21f6d72
@tmorton

Could we remove the explicit check for Rails.env, and just default to info? That seems cleaner to me.

@jeremy jeremy merged commit 4db5b55 into from
@tilsammans

Smart!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Apr 16, 2012
  1. @rosenfeld

    Make log_level explicit in production.rb template

    rosenfeld authored
    The 'production' environment name is currently checked for setting up
    the default log_level to 'info' but that won't work if the environment
    is copied to staging.rb, for instance. Better to have it explicitly set.
This page is out of date. Refresh to see the latest.
View
4 railties/lib/rails/generators/rails/app/templates/config/environments/production.rb.tt
@@ -32,8 +32,8 @@
# Force all access to the app over SSL, use Strict-Transport-Security, and use secure cookies.
# config.force_ssl = true
- # See everything in the log (default is :info).
- # config.log_level = :debug
+ # Set to :debug to see everything in the log.
+ config.log_level = :info
# Prepend all log lines with the following tags.
# config.log_tags = [ :subdomain, :uuid ]
Something went wrong with that request. Please try again.