Added section on Enabling the profiler.
Thanks to @sparksp for pointing it out.
This commit is contained in:
parent
4d6827ca14
commit
e854464a21
|
@ -1,9 +1,21 @@
|
|||
# Profiler
|
||||
|
||||
## Contents
|
||||
- [Enabling the Proiler](#enable)
|
||||
- [Logging to the Proiler](#logging)
|
||||
- [Timers and Benchmarking](#timers)
|
||||
|
||||
<a name="enable"></a>
|
||||
## Enabling the Profiler
|
||||
|
||||
To enable the profiler, you need to edit **application/config/application.php** and switch the profiler option to **true**.
|
||||
|
||||
'profiler' => true,
|
||||
|
||||
This will attach the profiler code to **all** responses coming back from your laravel install.
|
||||
|
||||
**Note:** As of the time of this writing a common problem with the profiler being enabled is any requests that return JSON will also include the profiler code, and destroy the JSON syntax in the response.
|
||||
|
||||
<a name="logging"></a>
|
||||
## Logging
|
||||
|
||||
|
@ -14,7 +26,7 @@ #### Logging to the profiler:
|
|||
Profiler::log('info', 'Log some information to the profiler');
|
||||
|
||||
<a name="timers"></a>
|
||||
## Timers
|
||||
## Timers and Benchmarking
|
||||
|
||||
Timing and benchmarking your app is simple with the ```tick()``` function on the profiler. It allows you to set various different timers in your app and will show you their performance when your app ends execution.
|
||||
|
||||
|
|
Loading…
Reference in New Issue