Contents

EffectiveLogging.setup do |config|
  # Configure Database Tables
  config.logs_table_name = :logs

  # Authorization Method
  #
  # This method is called by all controller actions with the appropriate action and resource
  # If the method returns false, an Effective::AccessDenied Error will be raised (see README.md for complete info)
  #
  # Use via Proc (and with CanCan):
  # config.authorization_method = Proc.new { |controller, action, resource| can?(action, resource) }
  #
  # Use via custom method:
  # config.authorization_method = :my_authorization_method
  #
  # And then in your application_controller.rb:
  #
  # def my_authorization_method(action, resource)
  #   current_user.is?(:admin)
  # end
  #
  # Or disable the check completely:
  # config.authorization_method = false
  config.authorization_method = Proc.new { |controller, action, resource| authorize!(action, resource) } # CanCanCan

  # Admin Screens Layout Settings
  config.layout = 'application'   # All EffectiveLogging controllers will use this layout

  # config.layout = {
  #   logs: 'application',
  #   admin_logs: 'admin',
  # }

  # EffectiveLogger.info('my message') macros
  # The following statuses are already present: info, success, error, view, change, email, sign_in, sign_out
  # Add more here
  config.additional_statuses = []

  #########################################
  #### Automatic Logging Functionality ####
  #########################################

  # Log all sent emails
  config.email_enabled = true

  # Log all sign ins (successful only)
  config.sign_in_enabled = true

  # Log all sign outs
  config.sign_out_enabled = false
end

Version data entries

25 entries across 25 versions & 1 rubygems

Version	Path
effective_logging-2.0.4	config/effective_logging.rb
effective_logging-2.0.3	config/effective_logging.rb
effective_logging-2.0.2	config/effective_logging.rb
effective_logging-2.0.1	config/effective_logging.rb
effective_logging-2.0.0	config/effective_logging.rb