Download the PHP package mikeevstropov/simple-logger without Composer
On this page you can find all versions of the php package mikeevstropov/simple-logger. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download mikeevstropov/simple-logger
More information about mikeevstropov/simple-logger
Files in mikeevstropov/simple-logger
Package simple-logger
Short Description Simple way to create instance of Monolog\Logger
License MIT
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 simple-logger
mikeevstropov/simple-logger
Simple way to create instance of Monolog\Logger
Installation
Add dependency mikeevstropov/simple-logger
Usage
LoggerFactory Interface
-
create
Returns instance of Monolog\Logger
Arguments:
file(string) - path to the log filelevel(string) - log level or "DEBUG" as defaultname(string) - name of logger or "logger" as default
Returns:
Monolog\Logger
Log Levels
Monolog supports the logging levels described by RFC 5424.
-
DEBUG (100): Detailed debug information.
-
INFO (200): Interesting events. Examples: User logs in, SQL logs.
-
NOTICE (250): Normal but significant events.
-
WARNING (300): Exceptional occurrences that are not errors. Examples: Use of deprecated APIs, poor use of an API, undesirable things that are not necessarily wrong.
-
ERROR (400): Runtime errors that do not require immediate action but should typically be logged and monitored.
-
CRITICAL (500): Critical conditions. Example: Application component unavailable, unexpected exception.
-
ALERT (550): Action must be taken immediately. Example: Entire website down, database unavailable, etc. This should trigger the SMS alerts and wake you up.
- EMERGENCY (600): Emergency: system is unusable.
Development
Clone
Go to project
Install dependencies
Run the tests
