Laravel实用工具介绍

一、官网地址

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

二、安装

composer require barryvdh/laravel-debugbar

三、配置文件路径

在.env中

# DEBUG模式开关
APP_DEBUG=true
# DEBUGBAR 开关
DEBUGBAR_ENABLED=false

config/debugbar.php

<?phpreturn [/*|--------------------------------------------------------------------------| 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,
];

四、使用方式

页面调用
接口调用

Laravel实用工具介绍 – Debugbar相关推荐

java比poi好用的工具五金零配件_好用不一定很贵---平价实用工具介绍
好用不一定很贵---平价实用工具介绍 2020-06-06 12:04:25 16点赞 92收藏 20评论创作立场声明:自用简单平价工具分享,注意一切脱离价格的对比都是耍流氓. 写这篇文章呢主要是看 ...
ARM开发软件及实用工具介绍
一.编译器介绍 1.ADS1.2 ADS是ARM公司的集成开发环境软件,他的功能非常强大.他的前身是SDT,SDT是ARM公司几年前的开发环境软件,目前SDT早已经不再升级.ADS包括了四个模 ...
java 实体属性个数_?Java中比较实用实体转换工具介绍
Java中比较实用实体转换工具介绍文中源码地址大家一般编码过程中,经常会遇到DO对象转化为DTO对象,对象和对象之间转换一般需要用到转换工具,毕竟使用getter/setter太过麻烦 DO:D ...
开发知识竞赛答题活动小程序过程中使用到的实用工具库介绍
前言我在做知识竞赛答题活动小程序经常需要处理一些比较基础的事情,比如时间.数组.数字.对象.字符串等处理,自己造轮子的话成本会比较高.这时候我们可以去找一些别人已经写好的开源模块或者开源库,我们直接 ...
介绍几个网络攻击中溯源的实用工具
介绍几个网络攻击中溯源的实用工具 1.Rootkit 查杀:http://www.chkrootkit.org Rootkit是一种特殊的恶意软件,它的功能是在安装目标上隐藏自身及指定的文件.进程和网 ...
aqlserver实用程序_sqlserver命令提示实用工具的介绍
除上述的图形化管理工具外,SQL Server2008还提供了大量的命令行实用工具,包括bcp.dtexec.dtutil.osql.reconfig.sqlcmd.sqlwb和tablediff等, ...
Lodash-一个一致性、模块化、高性能的 JavaScript 实用工具库介绍
官网:https://www.lodashjs.com 一.为什么选择 Lodash ? Lodash 通过降低 array.number.objects.string 等等的使用难度从而让 Java ...
如何使用 ASP.NET 实用工具加密凭据和会话状态连接字符串
文章编号 : 329290 最后修改 : 2006年4月10日修订 : 8.0 重要说明:本文包含有关如何修改注册表的信息.修改注册表之前,一定要先进行备份,并且一定要知道在发生问题时如何还原注册表 ...
Unix实用工具教程：《sed与awk》修订第三版清晰版
为什么80%的码农都做不了架构师?>>> Unix实用工具教程:<sed与awk>修订第三版清晰版本书介绍了一组名字奇特的Unix实用工具sed和awk,这组实用 ...

Laravel实用工具介绍 – Debugbar

Laravel实用工具介绍 – Debugbar相关推荐

最新文章

热门文章