Weave Code
Roadrunner Worker Laravel Package
spiral/roadrunner-worker
The common codebase for all RoadRunner binary workers—the high-performance PHP application server, load balancer, and process manager that replaces Nginx+FPM with PSR-7/PSR-17 compatible HTTP and HTTP/2 support.
spiral/roadrunner-worker is the shared PHP codebase for all RoadRunner binary workers. It implements the worker-side protocol that lets PHP processes communicate with the RoadRunner application server over STDIN/STDOUT, forming the foundation for HTTP, gRPC, and queue workers. Use it to build custom workers or extend existing ones through a consistent, low-level API.
- Base Worker class and
WorkerInterfacefor custom implementations - Goridge-compatible payload encoding and decoding
- Typed request/response message handling
- Environment and configuration helpers for worker processes
- Compatible with all RoadRunner worker plugins
Frequently asked questions about Roadrunner Worker
- What is spiral/roadrunner-worker used for?
- spiral/roadrunner-worker is the base PHP worker codebase for RoadRunner binary workers. It provides common worker bootstrap and runtime foundation so you can build RoadRunner-compatible workers instead of starting each request through PHP-FPM. It is used alongside spiral/roadrunner for the application server and spiral/roadrunner-http for PSR-7 HTTP workers. It is not a full Laravel framework bridge by itself.
- How do I install spiral/roadrunner-worker with Composer?
- Install it with Composer after confirming the resolved package name for your target version. The 3.7.x line uses spiral/roadrunner-worker, while the 3.8.0 release notes describe a rename to roadrunner/worker, so check Packagist and your lockfile before changing require lines. Pair it with the matching spiral/roadrunner server and HTTP worker packages. For RoadRunner binaries, the documented installer is spiral/roadrunner-cli and vendor/bin/rr get.
- Is spiral/roadrunner-worker compatible with Laravel?
- It can support Laravel on RoadRunner through a RoadRunner Laravel bridge, but this package is worker-runtime infrastructure rather than a Laravel-specific integration. You must verify that your chosen Laravel bridge is compatible with the renamed roadrunner/worker package and with PHP 8.2 before adopting 3.8.0. Treat the bridge compatibility check as a separate step from the worker package upgrade.
- What PHP version does spiral/roadrunner-worker require?
- The 3.8.0 release raises the minimum PHP version to 8.2, dropping PHP 8.0 and 8.1 support. Services still on 8.0 or 8.1 must stay on the 3.7.x line or complete a PHP runtime upgrade first. The #[\Override] refactor does not raise the floor beyond 8.2 because the attribute is inert unless reflected. Confirm the actual package metadata on Packagist before rollout.
- Why was spiral/roadrunner-worker renamed to roadrunner/worker?
- The 3.8.0 release performs a package rename to roadrunner/worker as a breaking identity change. Composer require lines, lockfile entries, and any references to the old package name must be updated, and consumers pinning spiral/roadrunner-worker will not receive this release. You should confirm whether the old name remains published as a metapackage or replace target, or whether the cutover is hard.
- How do I migrate from spiral/roadrunner-worker to roadrunner/worker?
- First validate that the roadrunner/worker package is published on Packagist and that the Git tag matches the changelog. Then update Composer require lines and lockfile entries in a single isolated change, and confirm the autoload namespace and any replace or provide shim. Do not combine this rename with a PHP-FPM to RoadRunner architecture migration; sequence the rename and PHP 8.2 upgrade separately from the runtime shift.
- Can I use spiral/roadrunner-worker on PHP 8.0 or PHP 8.1?
- No, the 3.8.0 release requires PHP 8.2 or newer. If your Laravel services are still on PHP 8.0 or 8.1, pin to the 3.7.x line until those services can be upgraded. Inventory PHP versions across targeted services before adopting the renamed package.
- Does spiral/roadrunner-worker work with roadrunner-laravel?
- Laravel integration is handled by a RoadRunner Laravel bridge such as roadrunner-laravel, not by this worker package alone. The release context says you must confirm that the relevant Laravel bridge is already compatible with the renamed roadrunner/worker package and PHP 8.2. Run a controlled pilot with your bridge version before estate-wide rollout.
- Is spiral/roadrunner-worker production ready?
- It is intended for long-running RoadRunner worker processes where per-request boot overhead must be minimized, and the architecture fit is strong. However, the 3.8.0 release has adoption risks: validate the future-dated changelog against the actual Git tag and Packagist entry, confirm the rename does not break dependency resolution, and account for low community adoption signals. A controlled pilot is safer than estate-wide rollout.
- What alternatives exist to spiral/roadrunner-worker for Laravel?
- Alternatives depend on whether you need RoadRunner specifically or just a high-performance PHP application server; this package is the base worker for RoadRunner, not a standalone server. If you stay on RoadRunner, the practical alternatives are pinning the 3.7.x spiral/roadrunner-worker line or adopting the renamed roadrunner/worker line with a compatible Laravel bridge. For non-RoadRunner stacks, evaluate other Laravel application server or worker runtimes against your PHP version and bridge support.
Weaver
How can I help you explore Laravel packages today?