Search Results for "log"

Laravel Telescope makes a wonderful companion to your local Laravel development environment. Telescope provides insight into the requests coming into your application, exceptions, log entries, database queries, queued jobs, mail, notifications, cache operations, scheduled tasks, variable dumps, and more. After installing Telescope, publish its assets using the telescope:install Artisan command. After installing Telescope, you should also run the migrate command in order to create the tables needed to store Telescope's data. ...

...Enter the code to be tested into the "PHP" or "JS" window and press "Run". The result will appear as Rendered or Raw HTML as you choose. In the background the code has been saved to a log file. Works on any machine running PHP. Log files are found in the Playground.log directory, sorted by year and month. A new log file is started every day and numbered accordingly. Warning! Do not use this program on a production site!

class.debug.php provide simple functions to set control infos in your code, with many options to output this info in your browser and/or write in a logfile - output of infos in browser, logfile or browser and logfile - (browser) output infos based on a error level - (browser) output infos compact or every message in a new line - (browser) output info based on a special pattern - (browser) output infos marked with special colors (html) - (logfile) log infos based on a error level - (logfile) log infos in a new file each execution, hour, day, week, month or year - (logfile) output infos compact or every message in a new line - (logfile) output info based on a special pattern TODO: - (logfile) create new logfiles based on a deadline - (logfile) create new logfiles based of a filesize - (logfile) create new logfiles based of a date - (logfile) create new logfiles based of a memorylimit look at debug_config to see all options

Debugging code has always been a tricky prospect. Most people use one of two methods: Either include "log" statements to see whats going on while running a routine, and then either delete them, or comment them out when they are done, (For legacy code, the commenting it out mechanism is often used so that the code is left to uncomment the next time that piece of code is worked on) or you can rely on a "debugger" to trace whats going on, and then look thru the more copious output. ...

PBL (aka PHP Bug lost) is a simple one-file script for use in any php websites that offers a console for debug and monitoring on your broser. It's based on FirePHP and PHP Quick Profiler. You can send log messages to the console, view SQL Querys, memory usage, list of user and server vars, files included, automatic detection of ajax request (like FireBug)... etc. Also PBL can send emails to the admin when a sql query fail or the app are using more memory or time that allowed. You can configure this. PBL don't have dependencies. ...

Log any javascript or php variables and it's back stack into file like php function debug_backtrace done. View the variables value and it's back stack info in web browser, and browser will synchronize with the log file using ajax.