4 * Debugbar Configuration Options
6 * Changes to these config files are not supported by BookStack and may break upon updates.
7 * Configuration should be altered via the `.env` file or environment variables.
8 * Do not edit this file unless you're happy to maintain any changes yourself.
13 // Debugbar is enabled by default, when debug is set to true in app.php.
14 // You can override the value by setting enable to true or false instead of null.
16 // You can provide an array of URI's that must be ignored (eg. 'api/*')
17 'enabled' => env('DEBUGBAR_ENABLED', false),
23 // DebugBar stores data for session/ajax requests.
24 // You can disable this, so the debugbar stores data in headers/session,
25 // but this can cause problems with large data collectors.
26 // By default, file storage (in the storage folder) is used. Redis and PDO
27 // can also be used. For PDO, run the package migrations first.
30 'driver' => 'file', // redis, file, pdo, custom
31 'path' => storage_path('debugbar'), // For file driver
32 'connection' => null, // Leave null for default connection (Redis/PDO)
33 'provider' => '' // Instance of StorageInterface for custom driver
36 // Vendor files are included by default, but can be set to false.
37 // This can also be set to 'js' or 'css', to only include javascript or css vendor files.
38 // Vendor files are for css: font-awesome (including fonts) and highlight.js (css files)
39 // and for js: jquery and and highlight.js
40 // So if you want syntax highlighting, set it to true.
41 // jQuery is set to not conflict with existing jQuery scripts.
42 'include_vendors' => true,
44 // The Debugbar can capture Ajax requests and display them. If you don't want this (ie. because of errors),
45 // you can use this option to disable sending the data through the headers.
46 // Optionally, you can also send ServerTiming headers on ajax requests for the Chrome DevTools.
48 'capture_ajax' => true,
49 'add_ajax_timing' => false,
51 // When enabled, the Debugbar shows deprecated warnings for Symfony components
52 // in the Messages tab.
53 'error_handler' => false,
55 // The Debugbar can emulate the Clockwork headers, so you can use the Chrome
56 // Extension, without the server-side code. It uses Debugbar collectors instead.
59 // Enable/disable DataCollectors
61 'phpinfo' => true, // Php version
62 'messages' => true, // Messages
63 'time' => true, // Time Datalogger
64 'memory' => true, // Memory usage
65 'exceptions' => true, // Exception displayer
66 'log' => true, // Logs from Monolog (merged in messages if enabled)
67 'db' => true, // Show database (PDO) queries and bindings
68 'views' => true, // Views with their data
69 'route' => true, // Current route information
70 'auth' => true, // Display Laravel authentication status
71 'gate' => true, // Display Laravel Gate checks
72 'session' => true, // Display session data
73 'symfony_request' => true, // Only one can be enabled..
74 'mail' => true, // Catch mail messages
75 'laravel' => false, // Laravel version and environment
76 'events' => false, // All events fired
77 'default_request' => false, // Regular or special Symfony request logger
78 'logs' => false, // Add the latest log messages
79 'files' => false, // Show the included files
80 'config' => false, // Display config settings
81 'cache' => false, // Display cache events
82 'models' => true, // Display models
85 // Configure some DataCollectors
88 'show_name' => true, // Also show the users name/email in the debugbar
91 'with_params' => true, // Render SQL with the parameters substituted
92 'backtrace' => true, // Use a backtrace to find the origin of the query in your files.
93 'timeline' => false, // Add the queries to the timeline
94 'explain' => [ // Show EXPLAIN output on queries
96 'types' => ['SELECT'], // ['SELECT', 'INSERT', 'UPDATE', 'DELETE']; for MySQL 5.6.3+
98 'hints' => true, // Show hints for common mistakes
104 'data' => false, //Note: Can slow down the application, because the data can be quite large..
107 'label' => true // show complete route on bar
113 'values' => true // collect cache values
117 // Inject Debugbar into the response
118 // Usually, the debugbar is added just before </body>, by listening to the
119 // Response after the App is done. If you disable this, you have to add them
120 // in your template yourself. See http://phpdebugbar.com/docs/rendering.html
123 // DebugBar route prefix
124 // Sometimes you want to set route prefix to be used by DebugBar to load
125 // its resources from. Usually the need comes from misconfigured web server or
126 // from trying to overcome bugs like this: http://trac.nginx.org/nginx/ticket/97
127 'route_prefix' => '_debugbar',
129 // DebugBar route domain
130 // By default DebugBar route served from the same domain that request served.
131 // To override default domain, specify it as a non-empty value.
132 'route_domain' => env('APP_URL', '') === 'http://bookstack.dev' ? '' : env('APP_URL', ''),