mirror of
https://github.com/Poniverse/Pony.fm.git
synced 2024-11-24 22:18:00 +01:00
00f24a5c12
* Adopt PSR-2 coding style The Laravel framework adopts the PSR-2 coding style in version 5.1. Laravel apps *should* adopt this coding style as well. Read the [PSR-2 coding style guide][1] for more details and check out [PHPCS][2] to use as a code formatting tool. [1]: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md [2]: https://github.com/squizlabs/PHP_CodeSniffer * Adopt PHP short array syntax Laravel 5 adopted the short array syntax which became available in PHP 5.4. * Remove SelfHandling from Jobs Jobs are self handling by default in Laravel 5.2. * Add new exceptions to `$dontReport` property * Shift core files * Shift Middleware Laravel 5.2 adjusts the `Guard` object used within middleware. In addition, new `can` and `throttles` middleware were added. * Shift Input to Request facade Laravel 5.2 no longer registers the `Input` facade by default. Laravel now prefers using the `Request` facade or the `$request` object within *Controllers* instead. Review the [HTTP Requests][1] documentation for more details. [1]: https://laravel.com/docs/5.2/requests * Shift configuration Laravel 5.2 introduces the `env` app configuration option and removes the `pretend` mail configuration option. In addition, a few of the default `providers` and `aliases` bindings were removed. * Shift Laravel dependencies * Shift cleanup * Updated composer.lock * Updated Middleware to 5.2 * Config update for Laravel 5.2 * [Laravel 5.2] Updated validation strings * Updated auth config * Updated to use middleware groups * Added laravel 5.2 sessions migration
169 lines
6.5 KiB
PHP
169 lines
6.5 KiB
PHP
<?php
|
|
|
|
return [
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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.
|
|
|
|
|
*/
|
|
|
|
'enabled' => null,
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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.
|
|
|
|
|
*/
|
|
'storage' => [
|
|
'enabled' => true,
|
|
'driver' => 'redis', // redis, file, pdo
|
|
'path' => storage_path() . '/debugbar', // For file driver
|
|
'connection' => null, // Leave null for default connection (Redis/PDO)
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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.
|
|
|
|
|
*/
|
|
|
|
'include_vendors' => true,
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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.
|
|
|
|
|
*/
|
|
|
|
'capture_ajax' => true,
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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.
|
|
|
|
|
*/
|
|
'clockwork' => false,
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| DataCollectors
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Enable/disable DataCollectors
|
|
|
|
|
*/
|
|
|
|
'collectors' => [
|
|
'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
|
|
'laravel' => false, // Laravel version and environment
|
|
'events' => false, // All events fired
|
|
'default_request' => false, // Regular or special Symfony request logger
|
|
'symfony_request' => true, // Only one can be enabled..
|
|
'mail' => true, // Catch mail messages
|
|
'logs' => false, // Add the latest log messages
|
|
'files' => false, // Show the included files
|
|
'config' => false, // Display config settings
|
|
'auth' => false, // Display Laravel authentication status
|
|
'gate' => false, // Display Laravel Gate checks
|
|
'session' => true, // Display session data
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Extra options
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Configure some DataCollectors
|
|
|
|
|
*/
|
|
|
|
'options' => [
|
|
'auth' => [
|
|
'show_name' => false, // Also show the users name/email in the debugbar
|
|
],
|
|
'db' => [
|
|
'with_params' => true, // Render SQL with the parameters substituted
|
|
'timeline' => false, // Add the queries to the timeline
|
|
'backtrace' => false, // EXPERIMENTAL: Use a backtrace to find the origin of the query in your files.
|
|
'explain' => [ // EXPERIMENTAL: Show EXPLAIN output on queries
|
|
'enabled' => false,
|
|
'types' => ['SELECT'], // array('SELECT', 'INSERT', 'UPDATE', 'DELETE'); for MySQL 5.6.3+
|
|
],
|
|
'hints' => true, // Show hints for common mistakes
|
|
],
|
|
'mail' => [
|
|
'full_log' => false
|
|
],
|
|
'views' => [
|
|
'data' => false, //Note: Can slow down the application, because the data can be quite large..
|
|
],
|
|
'route' => [
|
|
'label' => true // show complete route on bar
|
|
],
|
|
'logs' => [
|
|
'file' => null
|
|
],
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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
|
|
|
|
|
*/
|
|
|
|
'inject' => true,
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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
|
|
|
|
|
*/
|
|
'route_prefix' => '_debugbar',
|
|
|
|
];
|