Download the PHP package zero1/module-custom-logging without Composer

On this page you can find all versions of the php package zero1/module-custom-logging. 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?

Informations about the package module-custom-logging

Custom Logging

Allows configurable logging, on a per environment basis. Whilst still keeping the logging configuration in source control.

100% compatible with Mdoq

To setup you will need to add the following snippets to the appropriate files.
On you production sites make sure you change the stack value to production.
In addition to this if you are running multiple webheads you can the hardware_instance value to identify each web head. eg admin-01, web-asg-01 this will then be added to the logs.

env.php Config Example

config.php Config Example

Additional Information

The changes you make in app/etc/env.php are meant to be environment specific. In here you can configure the logging 'stack' you want to use. This value will be out of source control. The 'stack' is purely a nice name to a set of logging configuration defined in app/etc/config.php. In app/etc/config.php you can configure as many different stacks as you want e.g 'production', 'staging', 'local'. Each of these stacks is stored in source control allowing the stacks to be used by anyone on your code base.

In addition to be able to change the 'stack' with a single environment value, we can also add additional things to all loggers, so that all messages get this info. The default example adds four 'processors' that add extra info.

These will be added to all handlers:

These link to the loggers that are defined in etc/di.xml

How this is different from Magento core:


All versions of module-custom-logging with dependencies

PHP Build Version
Package Version
Requires php Version ~5.5.0|~5.6.0|^7.0.0
magento/product-community-edition Version ^2.0.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 zero1/module-custom-logging contains the following files

Loading the files please wait ....