Download the PHP package php-unified/log without Composer

On this page you can find all versions of the php package php-unified/log. 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?

Example code of php-unified/log

Informations about the package log

Build Status

PHP Unified Log

This package provides a standard for logging in PHP. The package aims to create a multi-use standard.

Please note that this package only contains interfaces for the implementation and a non-logging implementation.

Installation

Usage

Provided interfaces

PhpUnified\Log\Common\LoggerInterface

This interface provides a standard for implementing loggers into applications. It exposes three functions.

log

This function is meant for logging a message with a severity indication. The severity indication can be picked from the constants defined in the interface.

Constants

The constants in this class can be used to determine the severity of the log.

EMERGENCY

The system has become unuseable. Multiple components of the system have stopped working.

FATAL

A fatal(ity) is a complete failure of the application. Immediate action should be taken. Normal operation most likely can not be continued without action. The user experience is completely disrupted.

ERROR

An error is a significant failure in the application. These types of errors should be prioritized. Normal operation can continue, but might disrupt again. The user experience did get affected.

WARNING

A warning is a potential failure in the application. Normal operation can continue, but the underlying issue can result in additional issues with a greater severity. The user experience most likely didn't get affected.

NOTICE

A notice is a minor disruption in the application. Normal operation is possible. However the warning can have adverse affects if left untreated.

INFO

These logs are meant to supply information about the system. E.g. which processes have been run.

DEBUG

Logs information meant for developers. E.g. performance statistics.

PhpUnified\Log\Common\OptionalLoggingInterface

This interface provides a standard for an implementation which can optionally log information. This can be useful when less information should be logged in a production environment opposed to development environments.

PhpUnified\Log\Common\TransitLoggerInterface

This interface provides a standard for multi-logger. The implementation of this interface should function a pass-through to several other implementations of the LoggerInterface. This could be useful if logs should be stored in multiple places or in different formats.

For this interface, an implementation is provided. See: PhpUnified\Log\TransitLogger.

Require a logger

To create an implementation which requires a logger, implement the following snippet:

Optional logger

To create an implementation which can optionally log information, implement the following snippet:

Change log

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CODE_OF_CONDUCT for details.

MIT License

Copyright (c) GrizzIT

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

All versions of log with dependencies

PHP Build Version
Package Version
Requires php Version ^8.0
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 php-unified/log contains the following files

Loading the files please wait ....