be95496158
Moved more basic logic into application start to make it easier to hook into early life cycle events such as configuration loading while not introducing extra files into the framework. Signed-off-by: Taylor Otwell <taylorotwell@gmail.com>
69 lines
2.2 KiB
PHP
69 lines
2.2 KiB
PHP
<?php
|
|
|
|
return array(
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Ignored Error Levels
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Here you simply specify the error levels that should be ignored by the
|
|
| Laravel error handler. These levels will still be logged; however, no
|
|
| information about about them will be displayed.
|
|
|
|
|
*/
|
|
|
|
'ignore' => array(E_NOTICE, E_USER_NOTICE, E_DEPRECATED, E_USER_DEPRECATED),
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Error Detail
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Detailed error messages contain information about the file in which an
|
|
| error occurs, as well as a PHP stack trace containing the call stack.
|
|
| You'll want them when you're trying to debug your application.
|
|
|
|
|
| If your application is in production, you'll want to turn off the error
|
|
| details for enhanced security and user experience since the exception
|
|
| stack trace could contain sensitive information.
|
|
|
|
|
*/
|
|
|
|
'detail' => true,
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Error Logging
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| When error logging is enabled, the "logger" Closure defined below will
|
|
| be called for every error in your application. You are free to log the
|
|
| errors however you want. Enjoy the flexibility.
|
|
|
|
|
*/
|
|
|
|
'log' => false,
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Error Logger
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Because of the various ways of managing error logging, you get complete
|
|
| flexibility to manage error logging as you see fit. This function will
|
|
| be called anytime an error occurs within your application and error
|
|
| logging is enabled.
|
|
|
|
|
| You may log the error message however you like; however, a simple log
|
|
| solution has been setup for you which will log all error messages to
|
|
| text files within the application storage directory.
|
|
|
|
|
*/
|
|
|
|
'logger' => function($exception)
|
|
{
|
|
Log::exception($exception);
|
|
},
|
|
|
|
); |