Download the PHP package mblsolutions/audit-logging without Composer

On this page you can find all versions of the php package mblsolutions/audit-logging. 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 audit-logging

Audit Logging

Audit Logging for Laravel projects

Installation

The recommended method to install LaravelRepository is with composer

Laravel without auto-discovery

If you don't use auto-discovery, add the ServiceProvider to the providers array in config/app.php

Package configuration

Database Driver

If you would like to use the Database driver to store your audit logs, you will first need to create and run the database driver migration.

This will create a new migration in database/migrations, after creating this migration run the database migrations to create the new table.

`

Usage

The configuration and setup can be adjusted in the audit logging config file located in config/audit-logging.php. We recommend reading through the config file before enabling audit logging to ensure you have the optimum setup.

Enable/Disable Logging

Before logs are stored you will need to enable audit logging by setting the config values to true.

This can also be set in your .env file by using the corresponding environment variable

Audit Logging Middleware

To enable audit logging for routes there are multiple ways this can be achieved, middleware aliases has been created

The only differences with these middleware are the log type

Single Route

You can enable audit logging for a single route by applying the middleware to the route.

Or by using the fully qualified class name

Route Groups

You can apply the middleware to a group of routes.

Excluding Routes

You can exclude specific routes in a group of middleware.

Optional Model/Trait for Log Retrieval

We have included an AuditLog Model with a BindsDynamically trait which you can use if you'd like to use an eloquent model for retrieving and formatting data.

Using Model with BindsDynamically trait

In order to use the AuditLog model (or any model implementing the BindsDynamically trait) you need to instantiate it with a connection and table as in the example below:

You can then use the $auditLog as you would any eloquent model.

Archiving Logs

If you would like to archive your logs and continue with a fresh table then you can use the archive command by running:

`

If you have installed fresh from version 1.6.0 you are good to go, otherwise if you have an existing installation from an earlier version you should run the update migration to add an index to the audit logs created_at column (if you have not already). You just need to publish the update with:

`

and then remember to run

`

This should be done as soon as possible after your archiving as the more data in the table the longer the migration will take.

License

Audit Logging is free software distributed under the terms of the MIT license.


All versions of audit-logging with dependencies

PHP Build Version
Package Version
Requires php Version ^7.4|^8.0|^8.1
ext-json Version *
illuminate/contracts Version ^6.0|^7.0|^8.0|^9.0|^10|^11
illuminate/events Version ^6.0|^7.0|^8.0|^9.0|^10|^11
illuminate/database Version ^6.0|^7.0|^8.0|^9.0|^10|^11
illuminate/support Version ^6.0|^7.0|^8.0|^9.0|^10|^11
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 mblsolutions/audit-logging contains the following files

Loading the files please wait ....