Download the PHP package pushinbr/pam-laravel without Composer

On this page you can find all versions of the php package pushinbr/pam-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?

Example code of pushinbr/pam-laravel

Informations about the package pam-laravel

# Laravel on PAM **Keep Laravel. Replace the disposable runtime underneath it.** Production lifecycle, isolation, observability, queues, and deployment tooling for long-lived Laravel applications running on PAM. [![Release](https://img.shields.io/github/v/release/push-in/pam-laravel?style=flat-square&label=stable)](https://github.com/push-in/pam-laravel/releases) ![PHP](https://img.shields.io/badge/PHP-8.5-777BB4?style=flat-square&logo=php&logoColor=white) ![License](https://img.shields.io/github/license/push-in/pam-laravel?style=flat-square) **[Documentation](https://push-in.github.io/pam-docs/laravel/overview/) · [Why this exists](#why-this-exists) · [What you can build](#what-you-can-build) · [Quick start](#quick-start) · [Issues](https://github.com/push-in/pam-laravel/issues)**

Why this exists

Production lifecycle, isolation, observability, queues, and deployment tooling for long-lived Laravel applications running on PAM.
Role Framework integration
Execution path Laravel · Persistent PHP · PAM Runtime
This repository owns Laravel boot, request isolation, cleanup, diagnostics, and production commands
Boundary Laravel conventions and its package ecosystem remain Laravel

What you can build

Quick start

The PAM documentation covers prerequisites, production setup, and the complete workflow. PAM projects keep normal manifests and lockfiles; product features stay in the package that owns them.

Production tooling for Laravel 12 and 13 applications running on the PAM runtime.

Production lifecycle

PAM Laravel adds a request state guard to the web and api middleware groups. It rolls back leaked transactions, forgets authenticated users, restores the process locale and clears resolved facades after every request. Use strict mode in CI to turn detected state leakage into a failed request:

Application-specific cleanup can implement Pam\Laravel\Contracts\LifecycleHook and register it with LifecycleManager.

Operations

The default endpoints are:

Set PAM_LARAVEL_OBSERVABILITY_TOKEN to require a bearer token on metrics. The registry retains bounded route, query and state-violation data, preventing the observability layer itself from becoming a memory leak.

Zero-downtime releases

Prepare an immutable release inside PAM_DEPLOY_ROOT, run migrations and framework cache generation in the release, then activate it with pam:deploy. Activation uses an atomic symlink replacement and records the previous target for rollback. Destructive schema changes should follow expand/migrate/contract deployment discipline.

Process manifest

pam.processes.json represents commands as arrays, not shell strings. This keeps arguments unambiguous and avoids manifest command injection:

PAM's Laravel runtime remains conservative about request concurrency because Laravel applications and third-party packages can hold mutable process-global state. Scale with multiple isolated workers; certify lifecycle hooks under load before opting into more aggressive concurrency.

Support policy

The compatibility matrix tests PHP 8.4 with the maintained Laravel 12 release and the current Laravel 13 release. The public compatibility registry lives in the main PAM repository.

See the full production platform guide for OTLP traces, Nightwatch, PAM Cloud and Forge operations, autoscaling, MCP, package certification and reproducible benchmarks.

All versions of pam-laravel with dependencies

PHP Build Version
Package Version
Requires php Version ^8.4
laravel/framework Version ^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 pushinbr/pam-laravel contains the following files

Loading the files please wait ...