Download the PHP package de-swebhosting-flow-package/databaselog without Composer
On this page you can find all versions of the php package de-swebhosting-flow-package/databaselog. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download de-swebhosting-flow-package/databaselog
More information about de-swebhosting-flow-package/databaselog
Files in de-swebhosting-flow-package/databaselog
Package databaselog
Short Description Provides a Backend for writing log entries to the database and a logger for connecting log entries with accounts and optionally partys from the party framework.
License GPL-3.0+
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 databaselog
De.SWebhosting.DatabaseLog
This is a Flow framework package that brings you some logging features:
- You can store log messages in the database.
- You can search for log entries using a repository.
- You can store account / user information in the log entries and filter for them.
Install
If you want to use this package, you simply need to add a require statement to your composer.json file:
Hint! This package was tested with TYPO3 Flow Version 6.1 only. If you are having trouble with older versions please open an issue.
How to use it
Database backend
There are two possibilities to use the database backend for logging.
Inject databaseLogger in your objects
This package comes with a preconfigured PSR log identifier called databaseLogger. This logger only logs to
the database.
You can inject it by adding the related config in your Objects.yaml:
With this configuration the $logger poperty in your class will use the databseLogger log.
Configure backend in existing loggers
You can also add the database logger as an additional backend to existing logs or replace the default
backend by ajusting the configuration in Settings.yaml:
This overwrites the i18nLogger backend with the database backend.
To add it as additional backend, simply use another key than default:
Log repository
You can use the \De\SWebhosting\DatabaseLog\Domain\Repository\LogEntryRepository like any other Flow repository
to search for log entries. Inject it in your class and start querying.
It currently comes with a minimal selection of query methods. Please let me know if you need more.
Account action logger
A special feature of this package is the account action logger. It allows you to store log entries that are connected to an account or to a party (if the party framework is installed).
The account is passed to the logging backend in the additional data array in a parameter called
De.SWebhosting.DatabaseLog.Account. If a normal backend is used, this parameter will simply be stored as a
readable var dump.
If the DatabaseBackend of this package is used, the parameter will be interpreted and the account identifer and the authentication provider name will be stored in properties of the log entry model. This allows you to filter for log messages of a dedicated account.
If the party framework is installed and a party is connected to the provided account, the object identifier and the full name of the user will also be stored in the database.
