Download the PHP package nanuc/loggy without Composer

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

Loggy

This is a helper to include the Loggy in your Laravel projects. Loggy enables you to quickly send log messages to a central place where they are displayed in real-time.

Installation

Install via composer

You can install the package via composer:

Generate a key

Afterwards generate a key so that Loggy is able to identify logs coming from you:

The output of the command shows you your future Loggy link. Open this link now in a browser before you test your Loggy installation.

You can set the key LOGGY_KEY in .env to anything you want. Just remember that all apps with the same key share the same URL.

Test Loggy

You can send a test entry to Loggy:

If everything went right you should see two entries popping up on the openend website.

Usage

Just put the following in your Laravel code to send information to Loggy:

myMessage can be basically anything.

Time measurement

You can start and stop a time measurement with

The name is optional and defaults to "Measurement".

Blade

You can also use loggy in your Blade views.

More information

Why?

When starting to work with Laravel Vapor we realized how great this product of the Laravel team is! But our app showed different behaviour on the production system than in our development system. Finding the issues was very hard because logging in the Vapor console is not as intuitive as we were used to from our local systems. So we built a helper that just sends logging entries to a dashboard in realtime - "Loggy" was born. We asked ourselves the question: why not open it to any Laravel developer? We found no negative answer, so: here we go! And it's not just great for Vapor - it helps even with your local development.

What does it do with my data?

Receive it - display it - forget it. Data is persisted in no way. Which means your Loggy page has to be open in a browser to receive the data.


All versions of loggy with dependencies

PHP Build Version
Package Version
No informations.
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 nanuc/loggy contains the following files

Loading the files please wait ....