Download the PHP package data-dog/audit-bundle without Composer
On this page you can find all versions of the php package data-dog/audit-bundle. 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 audit-bundle
Audit Bundle
This bundle creates an audit log for all Doctrine ORM database related changes:
- Inserts and updates including their diffs and relation field diffs.
- Many to many relation changes, association and dissociation actions.
- If there is a user in token storage, they will be linked to the log.
- The audit entries are inserted within the same transaction during flush, if something fails the state remains clean.
Basically you can track any change from these log entries if they were managed through standard ORM operations.
NOTE: audit cannot track DQL or direct SQL updates or delete statement executions.
Install
First, install it with composer:
Then, add it in your bundles.
Finally, create the database tables used by the bundle:
Using Doctrine Migrations Bundle:
Using Doctrine Schema:
Usage
audit entities will be mapped automatically if you run schema update or similar. And all the database changes will be reflected in the audit log afterwards.
Unaudited Entities
Sometimes, you might not want to create audit log entries for particular entities.
You can achieve this by listing those entities under the unaudited_entities configuration
key in your config.yml, for example:
Specify Audited Entities
Sometimes, it is also possible, that you want to create audit log entries only for particular entities.
You can achieve it quite similar to unaudited entities. You can list them under the audited_entities
configuration key in your config.yml, for example:
You can specify either audited or unaudited entities. If both are specified, only audited entities would be taken into account.
Impersonation
Sometimes, you might also want to blame the impersonator user instead of the impersonated one.
You can archive this by adding the blame_impersonator configuration key in your config.yml, for example:
The default behavior is to blame the logged-in user, so it will ignore the impersonator when not explicitly declared.
Clean up old logs
To clean up old logs, use the following command:
You can specify retention-period, For format, see: https://www.php.net/manual/en/dateinterval.construct.php
License
The audit bundle is free to use and is licensed under the MIT license
All versions of audit-bundle with dependencies
doctrine/dbal Version ^3.2|^4.0
doctrine/doctrine-bundle Version ^2.9
doctrine/orm Version ^2.13|^3.0
symfony/security-bundle Version ^6.4 | ^7.0
symfony/framework-bundle Version ^6.4 | ^7.0
symfony/console Version ^6.4 | ^7.0