2017-05-18 25 views
10

Jak wyłączyć rejestrowanie SQL w środowisku produkcyjnym Rails 5.0.1? Dodałem to do mojego środowiska config/environments/production.rb, ale nadal widzę SQL zalogowany w moim pliku log/production.log. Oto mój pełny plik production.rbNie można wyłączyć rejestrowania SQL w moim środowisku produkcyjnym Rails

Rails.application.configure do 
    # Settings specified here will take precedence over those in config/application.rb. 

    # Code is not reloaded between requests. 
    config.cache_classes = true 

    # Eager load code on boot. This eager loads most of Rails and 
    # your application in memory, allowing both threaded web servers 
    # and those relying on copy on write to perform better. 
    # Rake tasks automatically ignore this option for performance. 
    config.eager_load = true 

    # Full error reports are disabled and caching is turned on. 
    config.consider_all_requests_local  = false 
    config.action_controller.perform_caching = false 

    # Enable Rack::Cache to put a simple HTTP cache in front of your application 
    # Add `rack-cache` to your Gemfile before enabling this. 
    # For large-scale production use, consider using a caching reverse proxy like 
    # NGINX, varnish or squid. 
    # config.action_dispatch.rack_cache = true 

    # Disable serving static files from the `/public` folder by default since 
    # Apache or NGINX already handles this. 
    config.serve_static_files = ENV['RAILS_SERVE_STATIC_FILES'].present? 

    # Compress JavaScripts and CSS. 
    config.assets.js_compressor = :uglifier 
    # config.assets.css_compressor = :sass 

    # Do not fallback to assets pipeline if a precompiled asset is missed. 
    config.assets.compile = false 

    # Asset digests allow you to set far-future HTTP expiration dates on all assets, 
    # yet still be able to expire them through the digest params. 
    config.assets.digest = true 

    # `config.assets.precompile` and `config.assets.version` have moved to config/initializers/assets.rb 

    # Specifies the header that your server uses for sending files. 
    # config.action_dispatch.x_sendfile_header = 'X-Sendfile' # for Apache 
    # config.action_dispatch.x_sendfile_header = 'X-Accel-Redirect' # for NGINX 

    # Force all access to the app over SSL, use Strict-Transport-Security, and use secure cookies. 
    # config.force_ssl = true 

    # Use the lowest log level to ensure availability of diagnostic information 
    # when problems arise. 
    config.log_level = :debug 

    # Prepend all log lines with the following tags. 
    # config.log_tags = [ :subdomain, :uuid ] 

    # Use a different logger for distributed setups. 
    # config.logger = ActiveSupport::TaggedLogging.new(SyslogLogger.new) 

    # Use a different cache store in production. 
    config.cache_store = :memory_store 

    # Enable serving of images, stylesheets, and JavaScripts from an asset server. 
    # config.action_controller.asset_host = 'http://assets.example.com' 

    # Ignore bad email addresses and do not raise email delivery errors. 
    # Set this to true and configure the email server for immediate delivery to raise delivery errors. 
    # config.action_mailer.raise_delivery_errors = false 

    # Enable locale fallbacks for I18n (makes lookups for any locale fall back to 
    # the I18n.default_locale when a translation cannot be found). 
    config.i18n.fallbacks = true 

    # Send deprecation notices to registered listeners. 
    config.active_support.deprecation = :notify 

    # Use default logging formatter so that PID and timestamp are not suppressed. 
    config.log_formatter = ::Logger::Formatter.new 

    # Do not dump schema after migrations. 
    config.active_record.dump_schema_after_migration = false 

    config.serve_static_files = true 
    config.assets.compile = true 

    # Raises error for missing translations 
    # config.action_view.raise_on_missing_translations = true 
    # Comment out the two lines withinn here so taht queries can be seen in the console 
    config.after_initialize do 
    ActiveRecord::Base.logger = Rails.logger.clone 
    ActiveRecord::Base.logger.level = Logger::INFO 
    end 

end 
+0

Ta odpowiedź ma kilka pomysłów, może warto spojrzeć na ... http://stackoverflow.com/questions/7759321/disable-rails-sql -logowanie w konsoli – SteveTurczyn

+0

Za mój plik, już to robię. – Dave

Odpowiedz

3

Per answer cytowany w komentarzach, musisz dodać następujący wiersz, aby wyłączyć rejestrowanie SQL: ActiveRecord::Base.logger = nil

Według Opublikowana config, trzeba ActiveRecord::Base.logger.level = Logger::INFO zamiast . Zastąp ten wiersz powyższym i logowanie SQL zostanie wyłączone.

Dodatkowo, zgodnie z zapisem here, można użyć ActiveRecord::Base.logger.level = 1, które zapobiegnie wyjątkom spowodowanym przez mniejsze poziomy dzienników (np. Informacje, ostrzeżenie itp.).

1

Dodaj następujący wiersz w production.rb

config.active_record.logger = nil 
Powiązane problemy