Download the PHP package zerethonapp/flow-laravel without Composer

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

Flow logo

flow-laravel

Tests Packagist Version Packagist Downloads

Laravel instrumentation adapter for Flow Phase 3 & 4 (real runtime traces).

Want to see it running before installing anything? flow-laravel-demo is a runnable Laravel app with 7 instrumented demo routes — clone it, composer install, and hit a route to see a real captured trace.

Contributing? See CONTRIBUTING.md. Found a security issue? See SECURITY.md, not a public issue. Release history: CHANGELOG.md. This project follows the Contributor Covenant.

Why Flow?

Most developers:

Flow shows the REAL bottleneck instantly:

Real Example

Your request takes 100ms. Where's the bottleneck?

Without Flow:

With Flow:

Conclusion: Database is NOT the problem. Focus on service logic instead.


What this package does

Scope (v1)

Included:

Not included yet:

Install

That's it! Flow will now automatically trace HTTP requests in every environment except testing.

Hit any route:

Check the trace:

Or browse individual traces:

Zero-Config Experience

By default, Flow:

No code changes required.

Connected Mode (Push Traces to Flow)

By default, traces only ever land in the local .zerethon/flow-history.json file above (Offline mode) — nothing leaves your machine/server unless you configure Connected mode. To have every captured trace pushed automatically to Flow, get a project's credentials from the Flow dashboard (shown once, at project creation) and add them to .env:

Then verify it's wired up correctly:

That's it — no other code changes. Traces still write to the local file too (Connected mode is additive, not a replacement); if any of the three env vars are missing, Flow just skips the push silently and behaves exactly as it did before.

Production is enabled by default (except_environments only excludes testing, see Configuration below) — the three FLOW_* env vars above are all that's needed on a real deployed environment. If you want Flow off in a specific environment (e.g. a staging server you don't want traced), publish the config (php artisan vendor:publish --tag=flow-config) and add that environment to except_environments — this check runs before anything else in FlowServiceProvider::boot(), so an excluded environment gets zero overhead, not just a silenced push.

Building an adapter for a different language/framework? flow-docs/ADAPTER_PROTOCOL.md documents the exact wire contract this package's push implements — it's plain HTTP+JSON, no PHP/Laravel-specific mechanism involved.

Configuration (Optional)

Publish config if you want to customize behavior:

The published config file at config/flow.php provides fine-grained control:

Enable/Disable

Sources

Control which data sources are active:

Source Options

Configure behavior per source:

Storage

Enable request capture middleware

Add middleware alias flow.trace to routes you want to capture.

Example:

Manual service and external tracing

Use the Facade:

Or use the global helper:

Generic trace method:

Assisted Tracing

Flow provides multiple ways to make tracing easier and less verbose:

Using the Traceable Trait

Add the trait to your service classes:

Using PHP Attributes (Future)

Note: Attribute-based tracing requires additional AOP/interceptor setup and is not yet fully implemented.

Output format

Traces are appended to:

Record shape matches Flow core storage:

Analyze with existing CLI

From the Laravel app root (where .zerethon/flow-history.json exists):

Raw JSON mode:

Demo scenario (real request trace)

Use middleware + manual service/external blocks:

Then call the route once and run:

Config

config/flow.php


All versions of flow-laravel with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
illuminate/support Version ^10.0|^11.0|^12.0|^13.0
illuminate/http Version ^10.0|^11.0|^12.0|^13.0
illuminate/database Version ^10.0|^11.0|^12.0|^13.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 zerethonapp/flow-laravel contains the following files

Loading the files please wait ...