Laravel实用工具介绍 – Debugbar

一、官网地址

https://github.com/barryvdh/laravel-debugbar

二、安装

composer require barryvdh/laravel-debugbar

三、配置文件路径

  1. 在.env中
    # DEBUG模式开关
    APP_DEBUG=true
    # DEBUGBAR 开关
    DEBUGBAR_ENABLED=false

     

  2. config/debugbar.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' => env('DEBUGBAR_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' => '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
    	],
    
    	/*
    	 |--------------------------------------------------------------------------
    	 | 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.
    	 |
    	 | Optionally, you can also send ServerTiming headers on ajax requests for the Chrome DevTools.
    	 */
    
    	'capture_ajax' => true,
    	'add_ajax_timing' => false,
    
    	/*
    	 |--------------------------------------------------------------------------
    	 | Custom Error Handler for Deprecated warnings
    	 |--------------------------------------------------------------------------
    	 |
    	 | When enabled, the Debugbar shows deprecated warnings for Symfony components
    	 | in the Messages tab.
    	 |
    	 */
    	'error_handler' => false,
    
    	/*
    	 |--------------------------------------------------------------------------
    	 | 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
    		'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
    	],
    
    	/*
    	 |--------------------------------------------------------------------------
    	 | Extra options
    	 |--------------------------------------------------------------------------
    	 |
    	 | Configure some DataCollectors
    	 |
    	 */
    
    	'options' => [
    		'auth' => [
    			'show_name' => true,
    			// Also show the users name/email in the debugbar
    		],
    		'db' => [
    			'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
    				'enabled' => false,
    				'types' => ['SELECT'],
    				// ['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',
    
    	/*
    	 |--------------------------------------------------------------------------
    	 | 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.
    	 */
    	'route_domain' => null,
    ];
    

     

四、使用方式

  1. 页面调用
  2. 接口调用
  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Laravel提供了一些值得调试的工具,可以帮助您识别和解决应用程序中的问题。以下是一些常用的调试工具: 1. Laravel Debugbar:这是一个强大的调试工具,提供了一个直观的仪表板,显示有关应用程序请求、数据库查询、日志、性能指标等的详细信息。您可以使用Composer安装Debugbar,并将其添加到应用程序中,以便在开发环境中使用。 2. Tinker:Tinker是Laravel的交互式命令行工具,类似于PHP的REPL(Read-Eval-Print Loop)。您可以使用Tinker来测试和调试代码,执行各种操作,如查看数据库记录、调用模型方法等。通过运行`php artisan tinker`命令,您可以进入Tinker环境并与应用程序进行交互。 3. 日志记录:Laravel提供了灵活的日志记录功能,可以帮助您记录和检查应用程序的各种操作和事件。您可以使用`Log`门面或`logger`辅助函数来记录自定义日志消息。日志文件通常位于`storage/logs`目录下,您可以查看这些文件以了解应用程序的运行情况。 4. 异常处理:Laravel具有强大的异常处理机制,可以捕获和处理应用程序中的异常。当发生异常时,Laravel会生成一个详细的错误页面,并记录异常信息。您可以根据异常信息来识别问题的根本原因,并进行相应的修复。 5. 路由和中间件调试:Laravel的路由和中间件系统是应用程序的核心组件。您可以使用`php artisan route:list`命令来查看应用程序的所有路由,并检查它们的配置和处理逻辑。通过在中间件中添加调试语句,您可以跟踪请求在中间件堆栈中的执行过程。 6. 调试工具包:除了上述工具外,还有一些第三方调试工具包可用于Laravel应用程序。例如,Clockwork提供了一个强大的调试和性能分析工具,可以帮助您深入了解应用程序的运行情况。可以使用Composer安装这些工具包,并按照其文档进行配置和使用。 这些工具将帮助您在开发和调试过程中更好地理解和解决Laravel应用程序中的问题。根据您的需求和偏好,选择适合您的工具进行调试。
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值