Download the PHP package adityadarma/laravel-database-logging without Composer
On this page you can find all versions of the php package adityadarma/laravel-database-logging. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download adityadarma/laravel-database-logging
More information about adityadarma/laravel-database-logging
Files in adityadarma/laravel-database-logging
Package laravel-database-logging
Short Description Logging activities database for laravel
License MIT
Homepage https://github.com/adityadarma/laravel-database-logging
FAQ
Example:
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 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.
Informations about the package laravel-database-logging
Laravel Database Logging
Laravel Database Logging is a feature that allows developers to store application logs in a database, rather than the default file-based storage. This feature provides a structured and organized approach to managing application logs, making it easier to query and analyze them.
Laravel Installation Instructions
-
From your projects root folder in terminal run:
-
Install config and asset to record the activities to:
-
Run the migration to add the table to record, before running please check morph key type on config to set type column:
*Note: Before migrate, please check config
/config/database-logging.phptype data on morp relation
Configuration
Laravel Database Logging can be configured in directly in /config/database-logging.php if you published the assets.
Or you can variables to your .env file.
Environment File
Here are the .env file variables available:
Separate logging database
Point DB_CONNECTION_LOGGING at any connection defined in config/database.php.
The database_loggings table is created on that connection, and the log rows
keep their own copy of the actor name in user_name, so the dashboard renders
correctly even though the logging database holds no users table.
Which column holds the display name is set per model in database-logging.php:
Note on the loggable relation: Eloquent forces a morphTo related model onto
the parent's connection when that model declares no connection of its own
(MorphTo::createModelByType). With a separate logging database $log->loggable
would therefore look for your users table inside the logging database. Use
$log->resolveLoggable(), which queries the related model on its own
connection, or read $log->name which already does it for you.
Usage
Middleware Usage
Events for laravel authentication scaffolding are listened for as providers and are enabled via middleware. You can add events to your routes and controllers via the middleware:
Example to start recording page views using middleware in web.php:
This middleware can be enabled/disabled in the configuration settings.
Trait Usage
Events can be recorded directly by using the trait. When using the trait you can customize the event description.
To use the trait:
-
Include the call in the head of your class file:
- Include the trait call in the opening of your class:
Routes
Laravel Activity Dashboard Routes
Set route access from file config database-logging.php
Purge
Remove data logger
Set limit days data log from file config database-logging.php then run the command
License
This Package is licensed under the MIT license. Enjoy!
