Download the PHP package phpgt/logger without Composer
On this page you can find all versions of the php package phpgt/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 logger
Simple logger for PHP applications.
Start logging with zero configuration. By default, the logger works as a static singleton - Log::error("You can't do that"); is all you need to get started. When you need to, you can configure the logger to send logs to different file/socket sources.
The aim of this library is minimalism. There are no plans to implement more logging sources than files and sockets. This simplifies the code into having a single responsibility, but remains modular to hook up to external scripts that handle logging to email addresses, Slack messages, AWS SQS, databases, etc.
Log levels
This library implements the PSR-3 interface. This means that throughout your code, you can decide to log at the levels listed below, and your environment can decide the minimum log level to report. For instance, it would probably be too verbose to log debug information on a production server. This is consistent with the Syslog protocol.
debug- Detailed debugging information.info- Interesting events.notice- Normal, but significant events.warning- Exceptional occurrences that are not errors.error- Runtime errors that do not require immediate action but should typically be logged and monitored.critical- Critical conditions.alert- Action must be taken immediately.emergency- System is unusable.
Static usage
Static classes should only be used when truly stateless. Logging is one example of a class that has no side effects on the running program, so the primary usage expectation is to use static methods of the Log class to perform logging.
It would be unnecessary to require passing an instance of the Log class around throughout all classes of your program, and it would be too opinionated to require the use of a dependency injection framework everywhere that logging is possible.
However, certain programs require advanced logging features that are only satisfiable with instances of the Log class, such as having different log sources for different areas of the program. Take a look at the examples directory to see how instantiation can be used for this purpose.
