Difference between revisions of "Extensions:Log Viewer"

From Lorekeeper Wiki
Jump to navigation Jump to search
(Created page with "{{subst:Extension Page}}")
Tag: 2017 source edit
 
Tag: 2017 source edit
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{Extensioninfobox|title=the extension's name|desc=A short description|auth=Author(s)|status=status (such as WIP, testing, stable)|github={{Github|user=username|branch=branch}}|LKVer=What Lorekeeper version the ext is built on|migration=yes/no|package=yes/no}}
+
{{Extensioninfobox|title=Log Viewer|desc=Allows admins to view/delete laravel logs in the storage directory without ssh-ing into their host. |auth=Cylunny|status=testing |github={{Github|user=Cylunny|branch=extension/log-viewer}}|LKVer=2.1.7|migration=no|package=no}}
<!-- Put a short summary of your extension here! -->
+
For those who don't want to ssh into their host just to check logs / deal with console commands to do so. You can now do it from the admin panel on your site itself!
 +
 
 
== Installation ==
 
== Installation ==
<!-- Describe installation. Include any requirements (such as packages), necessary commands, etc. -->
+
* pull & deal with merge conflicts
 +
* <code>php artisan optimize</code> x2
 +
* <code>php artisan update-extension-tracker</code>
 +
 
 
== Configuration ==
 
== Configuration ==
<!-- Is any configuration necessary? Describe it here! -->
+
It should work as is! Unless you changed the default log folder somehow.. it should be under storage/logs.
 +
 
 
== Usage ==
 
== Usage ==
<!-- Is there anything users should know about using your extension? -->
+
Go to your admin panel and under settings you should see the log viewer!
 +
 
 
== Troubleshooting ==
 
== Troubleshooting ==
<!-- Are there known issues or errors that require user action? Who should they contact, and where, for support? -->
+
If you have custom log entries in your normal laravel log files (named something like laravel-2024-07-07.log), you may have to exchange the parseLaravelLog() function with the generic parseLog() function in the LogController->getLog() function. This reads and prints everything and does not try build a collapsible stacktrace.
 +
 
 
== Images ==
 
== Images ==
<!-- Do you have any images to show what it looks like in action? -->
+
https://imgur.com/a/log-viewer-UylOjSY
 +
 
 
== See Also ==
 
== See Also ==
<!-- Any relevant other pages. You may consider linking to related extensions, for instance. -->
+
If this extension helped you, feel free to support me on [https://ko-fi.com/cylunny Kofi]!
 
 

Latest revision as of 22:26, 14 July 2024

Log Viewer
Description Allows admins to view/delete laravel logs in the storage directory without ssh-ing into their host.
Author(s) Cylunny
Status testing
Github extension/log-viewer
LK Version 2.1.7






For those who don't want to ssh into their host just to check logs / deal with console commands to do so. You can now do it from the admin panel on your site itself!

Installation

  • pull & deal with merge conflicts
  • php artisan optimize x2
  • php artisan update-extension-tracker

Configuration

It should work as is! Unless you changed the default log folder somehow.. it should be under storage/logs.

Usage

Go to your admin panel and under settings you should see the log viewer!

Troubleshooting

If you have custom log entries in your normal laravel log files (named something like laravel-2024-07-07.log), you may have to exchange the parseLaravelLog() function with the generic parseLog() function in the LogController->getLog() function. This reads and prints everything and does not try build a collapsible stacktrace.

Images

https://imgur.com/a/log-viewer-UylOjSY

See Also

If this extension helped you, feel free to support me on Kofi!