Weave Code
Process Laravel Package
php-standard-library/process
Typed, non-blocking PHP API for spawning, monitoring, and controlling child processes. Manage stdin/stdout/stderr streams, retrieve exit codes, and handle timeouts and signals with a clean, reliable interface for long-running and parallel tasks.
Typed, non-blocking API for spawning and managing child processes
Frequently asked questions about Process
- Can I replace all `exec()` or `shell_exec()` calls in Laravel with php-standard-library/process?
- Yes, but strategically. This package excels for structured process management (e.g., CLI tools, background jobs) but isn’t a drop-in for all cases—test performance and edge cases (like Windows vs. Unix) first. Start with critical workflows like deploy scripts or API integrations.
- How does this integrate with Laravel Queues for async process execution?
- Use the package’s non-blocking API to spawn processes in a Laravel job (e.g., `ProcessJob`). Return immediately while the process runs in the background. For output handling, stream results to a queue or database. Pair with Laravel’s `dispatch()` for scalability.
- What Laravel versions and PHP versions does this package support?
- The package is framework-agnostic but works with Laravel 10+ and PHP 8.2+. Verify compatibility with your Laravel version by checking the package’s `composer.json` constraints. For PHP 8.1 or older, test thoroughly—some features (like typed streams) may require updates.
- How do I handle process errors and failed executions in Laravel?
- Validate exit codes and stderr streams explicitly. Throw custom exceptions (e.g., `ProcessException`) and log them via Laravel’s logging system. For critical failures, trigger events (e.g., `ProcessFailed`) or use Laravel’s `Bus` to retry jobs with exponential backoff.
- Is this package secure against command injection attacks?
- Yes, but you must sanitize inputs. Avoid passing user-provided data directly to commands; use allowlists or escape arguments. For extra safety, wrap commands in a Laravel service with input validation before passing them to `Process::run()`.
- Can I use this for long-running processes (e.g., Docker builds, CI/CD tasks) in Laravel?
- Absolutely, but design for non-blocking execution. Offload tasks to queues or use Laravel’s `Process` facade (if extended) to manage lifecycle. Monitor memory/CPU usage via Laravel Telescope or custom metrics, and implement timeouts to prevent resource leaks.
- How does this compare to Symfony’s Process component for Laravel?
- This package is lighter (~30% fewer dependencies) and focuses on typed APIs, while Symfony’s Process offers broader features (e.g., progress tracking). Benchmark both for your use case—this library may outperform Symfony in microservices or CLI-heavy apps but lacks some enterprise features.
- How do I test process execution in PHPUnit without spawning real processes?
- Mock the `Process` class or use in-memory process emulation (e.g., `Process::fromString()`). For unit tests, verify output parsing and error handling logic. For integration tests, use Docker or temporary files to simulate real processes while keeping tests fast.
- Will this work in shared hosting or containerized environments (e.g., Docker, Heroku)?
- Yes, but test OS-specific behaviors (e.g., Windows vs. Unix signals). Shared hosting may restrict process execution—check `proc_open()` allowances. For containers, ensure the host OS supports the package’s features (e.g., `SIGTERM` handling). Use Docker for local testing.
- How can I extend this package to work seamlessly with Laravel’s Artisan commands?
- Create a Laravel service provider to bind the `Process` class to the container. Then, inject it into Artisan commands or use a facade (e.g., `Process::run()`). For example, replace `Artisan::call()` with `Process::run('command')` in custom commands, but handle output differently—stream results to the CLI.
Weaver
How can I help you explore Laravel packages today?