Download the PHP package iyogesharma/log-viewer without Composer

On this page you can find all versions of the php package iyogesharma/log-viewer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of iyogesharma/log-viewer

Informations about the package log-viewer

# LogViewer for Laravel ### Investigate Laravel logs without loading giant files into memory. Searchable log streams, bounded-memory indexing, operational analytics, and two modern opt-in themes—without a frontend build step. [![Release](https://img.shields.io/github/v/release/iYogesharma/logviewer-laravel?style=flat-square)](https://github.com/iYogesharma/logviewer-laravel/releases) [![Tests](https://img.shields.io/github/actions/workflow/status/iYogesharma/logviewer-laravel/run-tests.yml?branch=master&label=tests&style=flat-square)](https://github.com/iYogesharma/logviewer-laravel/actions) [![Laravel](https://img.shields.io/badge/Laravel-8%2B-ff2d20?style=flat-square&logo=laravel&logoColor=white)](#requirements) [![PHP](https://img.shields.io/badge/PHP-7.3%2B-777bb4?style=flat-square&logo=php&logoColor=white)](#requirements) [![License](https://img.shields.io/github/license/iYogesharma/logviewer-laravel?style=flat-square)](LICENSE.md) **A fork of [ARCANEDEV/LogViewer](https://github.com/ARCANEDEV/LogViewer) · current release line `2.x`** [Quick start](#quick-start) · [Themes](#themes) · [Large files](#large-file-streaming) · [Upgrade guide](UPGRADE.md) · [Changelog](CHANGELOG.md)
![The Observatory theme's dashboard: total events, high-severity share, error trend over time, and highest-risk files](_screenshots/observatory-dashboard.png) Observatory theme · see [all screenshots](#themes)

Why this fork?

This package is a fork of ARCANEDEV/LogViewer. It keeps the original Arcanedev\LogViewer\ namespace, configuration keys, routes and public API, so it installs as a drop-in replacement — see Migrating from arcanedev/log-viewer.

Traditional log viewers eventually hit the same wall: opening or searching a large file requires reading the whole thing into memory. Version 2 introduces a binary sidecar index and reads only the entries needed for the current request.

Capability What it provides
Bounded-memory streaming Paginate and search multi-megabyte logs without a whole-file read
Safe cold start Serve a bounded tail while an index is warming
Incremental indexing Append new log entries without rebuilding unchanged data
Format drivers Classic Laravel line logs and JSON logs behind one interface
Operational UI Error trends, severity health, pattern discovery, and whole-file searches
Familiar management Date and level filters, downloads, opt-in deletion, localization, and API access

Requirements

The dependency matrix is intentionally broad. Validate your exact PHP/Laravel combination in CI before a production upgrade.

Quick start

Installing straight from GitHub instead Add the repository to your application's `composer.json`, then require the package as usual:

Publish configuration when you need to customize storage, streaming, routes, or themes:

Open the viewer at:

The default remains bootstrap-5, so upgrading does not silently switch the interface.

Themes

Version 2 includes two self-contained themes. Both support automatic, light, and dark color modes and require no npm installation or asset compilation.

Observatory Console
Best for Support and operations teams Developers and message-first debugging
Dashboard Error trends, risk signals, severity health, highest-risk files Compact level distribution
Log files Non-scrolling investigation list Dense level-count grid
Investigation Dynamic dimensions and whole-file pattern searches Server search and visible-page filtering
Details Conditional stack/context expansion Conditional stack/context expansion
Copy tools Summaries, visible entries, complete entries Context and entry copy actions

Observatory

The Observatory theme turns indexed counts into support-oriented signals (dashboard screenshot above):

Pattern suggestions are sampled from the current page, but selecting one searches the complete selected log.

Console

The Console theme keeps the interface dense and direct:

Both themes apply the saved color mode before first paint to prevent light/dark flicker during navigation — the Console screenshots above show the same theme in dark and light modes.

Large-file streaming

Streaming is enabled by default for files above the inline threshold:

Warm indexes during deployment

Index one date:

When logs live on a read-only or shared mount, configure a dedicated writable directory:

Indexes are disposable caches. Source log files remain authoritative.

Bounded UI analytics

Dynamic pattern discovery intentionally has hard limits:

The interface shows the number of entries and bytes sampled. Applying a suggested value uses the normal server search route across the complete file.

Log formats

The streaming registry supports:

Pattern discovery does not require JSON. It can infer useful values from route-like text, labeled fields, environments, messages, classes, services, and optional context data.

Custom formats can be added through the format-driver contract. Test representative production logs before enabling streaming globally.

Configuration

The main options live in config/log-viewer.php:

Delete controls

Log deletion is destructive and irreversible, so the delete buttons in the two v2 themes are hidden by default:

Set it to true — or bind it to an environment variable — to show them:

This flag controls the UI of the observatory and console themes only. The log-viewer::logs.delete route stays registered, because the bootstrap themes still use it; apply route middleware if deletion must be forbidden outright.

Detailed package documentation remains available in:

  1. Installation and setup
  2. Configuration
  3. Usage
  4. Upgrading from 1.2.x

Migrating from arcanedev/log-viewer

The namespace, facade, configuration keys, route names, views and published assets are unchanged, so switching packages is a Composer operation:

Your existing config/log-viewer.php keeps working — merge the new streaming and delete keys when convenient. Existing Arcanedev\LogViewer\ imports, LogViewer:: facade calls and log-viewer:: route names need no edits.

The one code change to check for: if your application implements the Arcanedev\LogViewer\Contracts\LogViewer contract itself, add the new logForViewer($date) method. See the upgrade guide.

Upgrading to v2

Version 2 contains public-contract and runtime changes. Before deployment:

  1. Merge the new configuration.
  2. Update custom LogViewer contract implementations with logForViewer($date).
  3. Prepare a writable index directory.
  4. Test representative line and JSON logs.
  5. Warm large indexes if first-request latency matters.

See the complete upgrade guide, including opt-out and rollback instructions.

Testing

The suite covers classic behavior, streaming indexes, format handling, PCRE safety, and real-route rendering for both modern themes.

Localization

The package includes translations for Arabic, Bengali, Bulgarian, Chinese, Dutch, English, Estonian, French, German, Hungarian, Indonesian, Italian, Japanese, Korean, Malay, Persian, Polish, Portuguese, Romanian, Russian, Sinhala, Spanish, Swedish, Thai, Turkish, Ukrainian, and Uzbek.

Legacy Bootstrap preview

Show the inherited Bootstrap interface ![Bootstrap dashboard](_screenshots/1-dashboard.jpg) ![Bootstrap logs list](_screenshots/2-logs-list.jpg) ![Bootstrap single log](_screenshots/3-single-log.jpg)

Security

Please do not report security vulnerabilities through public issues. Contact the repository maintainer privately with reproduction details and affected versions.

Credits

This fork builds on the original ARCANEDEV LogViewer project and its contributors, and remains MIT licensed.

License

Released under the MIT License.

All versions of log-viewer with dependencies

PHP Build Version
Package Version
Requires php Version >=7.3
ext-json Version *
arcanedev/support Version >=8.0
psr/log Version ^1.0|^2.0|^3.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package iyogesharma/log-viewer contains the following files

Loading the files please wait ...