Download the PHP package websk/php-logger without Composer
On this page you can find all versions of the php package websk/php-logger. 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 php-logger
WebSK php-logger
websk/php-logger stores changes to WebSK entities and provides Slim routes for browsing object history and comparing revisions.
Requirements
- PHP 8.3, 8.4, or 8.5; PHP 8.5.11 is used for the release checks
- Composer 2
ext-mbstringandext-pdo_mysql- MySQL
- one cache backend supported by
websk/php-cacheand its PHP extension or client package
The bundled demo configuration uses Memcached. Install the memcached PHP extension and run a Memcached server before using that configuration. Redis and Memcache can be selected when their corresponding runtime dependencies are installed.
Installation
Configuration
Copy config/config.default.php to config/config.php, then update the database, cache, URL, and filesystem settings. The local configuration file is ignored by Git.
The user link integration uses two independent settings:
logger.user_service_container_nameis the PSR-11 identifier of the user entity service;logger.user_profile_route_nameis the named Slim route used to create profile links.
Either setting can be left empty when user profile links are not required. user_full_id itself is nullable.
Database
Create the configured MySQL database and apply dumps/db_logger.sql through the WebSK DB migration command:
For interactive migration handling, use:
The migration normalizes existing nullable text values before applying the non-null constraints expected by the typed LoggerEntry entity. It also adds an (object_full_id, id) index for previous-revision lookups.
Demo
After configuring the database and cache backend:
Open http://localhost:8000.
Serialized entity data
The logger restores serialized application entities to display historical field values. The logger database must therefore be treated as trusted input. Do not import serialized values from untrusted sources. Invalid serialized records are rejected and rendered as unavailable history.
Development
Install development dependencies and run all checks:
The check script runs PHP syntax checks, PHPUnit, and PHPStan at level max.
The optional MySQL integration test expects an already migrated disposable database:
Before packaging a release, also run:
License
MIT. See LICENSE.
All versions of php-logger with dependencies
ext-mbstring Version *
ext-pdo_mysql Version *
slim/slim Version 4.15.*
websk/php-config Version 2.2.*
websk/php-db Version 3.0.*
websk/php-crud Version 4.0.*
websk/php-entity Version 3.0.*
websk/php-slim Version 2.4.*
websk/php-utils Version 3.0.*
websk/php-view Version 3.1.*