ldc-mesbr-app/config/debugbar.php

236 lines
8 KiB
PHP
Raw Permalink Normal View History

2019-01-15 14:17:15 +01:00
<?php
return [
/*
2025-04-03 09:30:16 +02:00
|--------------------------------------------------------------------------
| Debugbar Settings
|--------------------------------------------------------------------------
|
| Debugbar is enabled by default, when debug is set to true in app.php.
| You can override the value by setting enable to true or false instead of null.
|
| You can provide an array of URI's that must be ignored (eg. 'api/*')
|
*/
2019-01-15 14:17:15 +01:00
'enabled' => env('DEBUGBAR_ENABLED', null),
'except' => [
2025-04-03 09:30:16 +02:00
],
2019-01-15 14:17:15 +01:00
/*
2025-04-03 09:30:16 +02:00
|--------------------------------------------------------------------------
| Storage settings
|--------------------------------------------------------------------------
|
| DebugBar stores data for session/ajax requests.
| You can disable this, so the debugbar stores data in headers/session,
| but this can cause problems with large data collectors.
| By default, file storage (in the storage folder) is used. Redis and PDO
| can also be used. For PDO, run the package migrations first.
|
*/
2019-01-15 14:17:15 +01:00
'storage' => [
'enabled' => true,
2025-04-03 09:30:16 +02:00
'driver' => 'file',
// redis, file, pdo, custom
'path' => storage_path('debugbar'),
// For file driver
'connection' => null,
// Leave null for default connection (Redis/PDO)
'provider' => ''
// Instance of StorageInterface for custom driver
2019-01-15 14:17:15 +01:00
],
/*
2025-04-03 09:30:16 +02:00
|--------------------------------------------------------------------------
| Vendors
|--------------------------------------------------------------------------
|
| Vendor files are included by default, but can be set to false.
| This can also be set to 'js' or 'css', to only include javascript or css vendor files.
| Vendor files are for css: font-awesome (including fonts) and highlight.js (css files)
| and for js: jquery and and highlight.js
| So if you want syntax highlighting, set it to true.
| jQuery is set to not conflict with existing jQuery scripts.
|
*/
2019-01-15 14:17:15 +01:00
'include_vendors' => true,
/*
2025-04-03 09:30:16 +02:00
|--------------------------------------------------------------------------
| Capture Ajax Requests
|--------------------------------------------------------------------------
|
| The Debugbar can capture Ajax requests and display them. If you don't want this (ie. because of errors),
| you can use this option to disable sending the data through the headers.
|
| Optionally, you can also send ServerTiming headers on ajax requests for the Chrome DevTools.
*/
2019-01-15 14:17:15 +01:00
'capture_ajax' => true,
'add_ajax_timing' => false,
/*
2025-04-03 09:30:16 +02:00
|--------------------------------------------------------------------------
| Custom Error Handler for Deprecated warnings
|--------------------------------------------------------------------------
|
| When enabled, the Debugbar shows deprecated warnings for Symfony components
| in the Messages tab.
|
*/
2019-01-15 14:17:15 +01:00
'error_handler' => false,
2021-04-27 17:29:47 +02:00
2019-01-15 14:17:15 +01:00
/*
2025-04-03 09:30:16 +02:00
|--------------------------------------------------------------------------
| Clockwork integration
|--------------------------------------------------------------------------
|
| The Debugbar can emulate the Clockwork headers, so you can use the Chrome
| Extension, without the server-side code. It uses Debugbar collectors instead.
|
*/
2019-01-15 14:17:15 +01:00
'clockwork' => false,
/*
2025-04-03 09:30:16 +02:00
|--------------------------------------------------------------------------
| DataCollectors
|--------------------------------------------------------------------------
|
| Enable/disable DataCollectors
|
*/
2019-01-15 14:17:15 +01:00
'collectors' => [
2025-04-03 09:30:16 +02:00
'phpinfo' => true,
// Php version
'messages' => true,
// Messages
'time' => true,
// Time Datalogger
'memory' => true,
// Memory usage
'exceptions' => true,
// Exception displayer
'log' => true,
// Logs from Monolog (merged in messages if enabled)
'db' => true,
// Show database (PDO) queries and bindings
'views' => true,
// Views with their data
'route' => true,
// Current route information
'auth' => true,
// Display Laravel authentication status
'gate' => true,
// Display Laravel Gate checks
'session' => true,
// Display session data
'symfony_request' => true,
// Only one can be enabled..
'mail' => true,
// Catch mail messages
'laravel' => false,
// Laravel version and environment
'events' => false,
// All events fired
'default_request' => false,
// Regular or special Symfony request logger
'logs' => false,
// Add the latest log messages
'files' => false,
// Show the included files
'config' => false,
// Display config settings
'cache' => false,
// Display cache events
2019-01-15 14:17:15 +01:00
],
/*
2025-04-03 09:30:16 +02:00
|--------------------------------------------------------------------------
| Extra options
|--------------------------------------------------------------------------
|
| Configure some DataCollectors
|
*/
2019-01-15 14:17:15 +01:00
'options' => [
'auth' => [
2025-04-03 09:30:16 +02:00
'show_name' => true,
// Also show the users name/email in the debugbar
2019-01-15 14:17:15 +01:00
],
'db' => [
2025-04-03 09:30:16 +02:00
'with_params' => true,
// Render SQL with the parameters substituted
'backtrace' => true,
// Use a backtrace to find the origin of the query in your files.
'timeline' => false,
// Add the queries to the timeline
'explain' => [
// Show EXPLAIN output on queries
2019-01-15 14:17:15 +01:00
'enabled' => false,
2025-04-03 09:30:16 +02:00
'types' => ['SELECT'],
// ['SELECT', 'INSERT', 'UPDATE', 'DELETE']; for MySQL 5.6.3+
2019-01-15 14:17:15 +01:00
],
2025-04-03 09:30:16 +02:00
'hints' => true,
// Show hints for common mistakes
2019-01-15 14:17:15 +01:00
],
'mail' => [
'full_log' => false
],
'views' => [
2025-04-03 09:30:16 +02:00
'data' => false,
// Note: Can slow down the application, because the data can be quite large..
2019-01-15 14:17:15 +01:00
],
'route' => [
2025-04-03 09:30:16 +02:00
'label' => true
// show complete route on bar
2019-01-15 14:17:15 +01:00
],
'logs' => [
'file' => null
],
'cache' => [
2025-04-03 09:30:16 +02:00
'values' => true
// collect cache values
2019-01-15 14:17:15 +01:00
],
],
/*
2025-04-03 09:30:16 +02:00
|--------------------------------------------------------------------------
| Inject Debugbar in Response
|--------------------------------------------------------------------------
|
| Usually, the debugbar is added just before </body>, by listening to the
| Response after the App is done. If you disable this, you have to add them
| in your template yourself. See http://phpdebugbar.com/docs/rendering.html
|
*/
2019-01-15 14:17:15 +01:00
'inject' => true,
/*
2025-04-03 09:30:16 +02:00
|--------------------------------------------------------------------------
| DebugBar route prefix
|--------------------------------------------------------------------------
|
| Sometimes you want to set route prefix to be used by DebugBar to load
| its resources from. Usually the need comes from misconfigured web server or
| from trying to overcome bugs like this: http://trac.nginx.org/nginx/ticket/97
|
*/
2019-01-15 14:17:15 +01:00
'route_prefix' => '_debugbar',
/*
2025-04-03 09:30:16 +02:00
|--------------------------------------------------------------------------
| DebugBar route domain
|--------------------------------------------------------------------------
|
| By default DebugBar route served from the same domain that request served.
| To override default domain, specify it as a non-empty value.
*/
2019-01-15 14:17:15 +01:00
'route_domain' => null,
];