README

Laravel Octane lifecycle, powered by Rust and Tokio.
Connect PAM's native HTTP transport to Octane while Octane keeps ownership of Laravel isolation and worker lifecycle.

Install · Commands · How it works · Compatibility · Docs · Issues

Install

In a Laravel application on PAM:

pam init my-app --template laravel
cd my-app
pam composer require laravel/octane pushinbr/pam-octane
pam octane:start

The defaults are production-safe and require no configuration. PAM Octane requires the PAM runtime: running php artisan pam:octane reports a clear error because ordinary PHP CLI does not contain PAM's native server; use pam artisan or pam octane:start.

Commands

pam octane:start     # start Laravel Octane on the PAM supervisor
pam octane:status    # inspect the PAM Octane application
pam octane:reload    # reload without downtime
pam octane:stop      # stop the application

octane:start runs pam up artisan --name pam-octane ... -- pam:octane; arguments before -- go to the supervisor, arguments after it to the server.

How it works

PAM Octane connects PAM's native HTTP transport directly to Laravel Octane's worker. Octane continues to own application isolation, lifecycle events and request cleanup; PAM owns PHP Embed, networking, streaming, supervision and Tokio-powered infrastructure.

HTTP → PAM / Tokio → PamClient → Octane Worker → Laravel
HTTP ← PAM / Tokio ← PamClient ← Octane Worker ← Laravel

PAM already embeds PHP and provides a persistent native HTTP runtime. This package deliberately does not duplicate Octane's Laravel lifecycle. It adapts PAM's request and response objects to Octane's public Client contract and then uses the real Laravel\Octane\Worker. That gives an application:

• one warm Laravel application per worker;
• Octane's request sandbox and lifecycle events;
• PAM's bounded streaming and client backpressure;
• correct cookies, uploads, HEAD, streamed and binary responses;
• one safe Laravel execution slot per worker;
• normal Laravel package discovery and configuration.

Configure

To customize limits, publish the small configuration file:

pam artisan vendor:publish --tag=pam-octane-config

Environment variables include:

PAM_HOST=127.0.0.1
PAM_PORT=8000
PAM_REQUEST_TIMEOUT_MS=30000
PAM_MAX_BODY_BYTES=2097152
PAM_MAX_RESPONSE_BYTES=268435456

maxConcurrentRequests is intentionally fixed to 1 for Laravel. Framework managers and facades contain process-global mutable state. Scale safely with multiple supervised PAM workers instead of overriding that boundary.

Supervised clusters, route-aware worker pools, systemd, troubleshooting and the quality suite are in Production.

Compatibility

Runtime capabilities

• generational reload, status, stop and control-plane health;
• route-aware worker pools with crash and memory isolation;
• cooperative Fiber scheduling and HTTP/Redis clients;
• isolated bounded PDO and process pools for blocking work;
• production response cache with tags, authenticated invalidation, collapse and stale-while-revalidate;
• bounded route metrics plus Pulse, Telescope and OpenTelemetry integration.

Support and repository model

Usage questions belong in PAM GitHub Discussions. Reproducible defects use the main PAM issue tracker, and vulnerabilities must use private GitHub Security Advisories as described in SECURITY.md.

PAM Octane is developed in packages/octane alongside the runtime so transport and lifecycle changes can be tested atomically. It remains an independent, optional Composer package: applications that do not use Laravel or Octane do not install it.

Docs

• Laravel on PAM
• Production: supervised cluster, worker pools, systemd, troubleshooting, quality
• Changelog
• Contributing

Part of the PAM ecosystem

PAM runs PHP natively on servers, desktops and phones. This repository is one piece of it.

_{Docs: push-in.github.io/pam-docs · Issues}

_{Apache License 2.0 · Made in Brazil by Pushin}