Download the PHP package ensi/laravel-auditing without Composer
On this page you can find all versions of the php package ensi/laravel-auditing. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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-auditing
Laravel Auditing
Opiniated fork of owen-it/laravel-auditing
Installation
You can install the package via composer:
Publish the migrations with:
Migrate from 0.2.x to 0.3.0
- Publish new migration
php artisan vendor:publish --provider="Ensi\LaravelAuditing\LaravelAuditingServiceProvider" --tag=migrations-0.3 - If the config
laravel-auditing.phpis published, then replace theresolver.uservalue withEnsi\LaravelAuditing\Resolvers\UserResolver::class
Version Compatibility
| Laravel Auditing | Laravel | PHP |
|---|---|---|
| ^0.1.2 | ^7.x || ^8.x | ^8.0 |
| ^0.2.0 | ^7.x || ^8.x | ^8.0 |
| ^0.3.0 | ^7.x || ^8.x | ^8.0 |
| ^0.3.1 | ^8.x || ^9.x | ^8.0 |
| ^0.3.5 | ^8.x || ^9.x || ^10.x || ^11.x | ^8.0 |
| ^0.4.0 | ^9.x || ^10.x || ^11.x | ^8.1 |
Basic Usage
By default, no modification history is saved for models.
To enable logging for a specific model, you need to add the Support s Audit trait and the Auditable interface to it
If we change the data of the child models from a logical point of view and want this change to take place under the parent model in the history, it is necessary to set the root entity (i.e. the model) in the transaction before changing the data.
This is done through the Transaction facade or the manager \\Ensi\\LaravelAuditing\\Transactions\\ExtendedTransactionManager
To add data to the history about who made the changes (a specific user, or, for example, a console command), again, you need to do this before changing the data, but through the Subject facade or the injection of \\Ensi\\LaravelAuditing\\Resolvers\\SubjectManager
The subject does not unbind after the transaction is completed.
It can be unlinked manually by calling the Subject::detach() method.
When processing http requests, you can set the subject in middleware. In console commands and handlers, event queues are reassigned during execution.
The subject can be any entity that supports the interface \Ensi\LaravelAuditing\Contracts\Principal.
If the subject is an ongoing task, for example, importing from a file, then it can return the ID of the user who created the task in the getUserIdentifier() method, and return the name of the imported file as the name.
In the user model, the getAuthIdentifier() and getUserIdentifier() methods return the same identifier.
Also, unlike the original package, not only the changed fields are saved in the history, but also the complete state of the model object at the time of the change.
Contributing
Please see CONTRIBUTING for details.
Testing
- composer install
- composer test
Security Vulnerabilities
Please review our security policy on how to report security vulnerabilities.
License
The MIT License (MIT). Please see License File for more information.
