Download the PHP package mhrshuvo/journey-log without Composer

On this page you can find all versions of the php package mhrshuvo/journey-log. 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?

Informations about the package journey-log

JourneyLog Laravel Package

JourneyLog is the "Black Box" for your Laravel application. Designed specifically for high-stakes industries like Flight, Bus, and Hotel Reservations or Dropshipping, it creates a secure, organized, and session-isolated audit trail of every user interaction and 3rd-party API response.

Stop digging through massive, messy log files. Start seeing the full story of every booking.

🌟 Why JourneyLog?

In reservation systems, 3rd-party APIs (GDS, Wholesalers, Suppliers) change prices and availability in milliseconds. When a customer claims a price mismatch or a booking fails, you need evidence.

Installation

Server Setup & Permissions

Required Permissions

Ensure your web server user has proper permissions:

Common Server Issues & Solutions

1. Permission Denied Errors

If you see permission errors in logs:

2. SELinux Issues (RHEL/CentOS)

3. Shared Hosting

4. Docker Container Issues

Automatic Cleanup Scheduler

The package includes automatic cleanup of old files. Ensure Laravel's scheduler is running:

Manual Cleanup

Configuration

Publish the config file:

Environment Variables

Add to your .env file:

Data Masking

Protect sensitive information by automatically masking specified field names in your logs. The package includes built-in protection for common sensitive fields and allows customization.

Default Protected Fields

The following fields are automatically masked by default:

Usage Example

Generated Log Output

Nested Data Masking

Masking works recursively through nested arrays:

Customizing Masked Fields

You can customize which fields are masked by modifying the configuration:

config/journeylog.php:

Case-Insensitive Matching

Field matching is case-insensitive, so all of these would be masked:

Usage

Basic Logging

Example Use Cases

Example 1: Web Application User Journey

Setup Route:

Controller Implementation:

Request Flow:

Example 2: API Application with Mobile App

Setup Route:

Mobile App Implementation:

API Controller Implementation:

Request Flow:

Generated Log Files

Example: /storage/logs/journeys/search/journey-abc123def456.json

Example: /storage/logs/journeys/cart/journey-abc123def456.json

Example: /storage/logs/journeys/checkout/journey-abc123def456.json

Middleware Setup

Journey ID Resolution Priority

The middleware resolves journey IDs in this order for both web and API:

  1. Header: X-Journey-ID (works for both web and API)
  2. Session: journey_id (web routes only)
  3. Generated: Random 12-character string (fallback)

API Usage

For API clients, include the journey ID in headers:

File Structure

Files are organized as:

Troubleshooting

Check Permissions

Enable Fallback Logging

The package automatically falls back to Laravel's default logging if it can't write journey files. Check your application logs:

Debug Mode

Enable debug mode to see permission issues:

Production Deployment Checklist

Support

If you encounter permission issues, the package will automatically log errors to Laravel's default log system for debugging.


All versions of journey-log with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
illuminate/support Version ^10.0|^11.0|^12.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 mhrshuvo/journey-log contains the following files

Loading the files please wait ...