- What is foxws/laravel-podman used for in Laravel applications?
- It integrates Podman container management with Laravel and adds Podman Quadlet support for containerized environments. The package is designed to provide Laravel tooling such as service providers, configuration, and artisan commands, along with presets like ondemand for queue worker management. It is aimed at teams standardizing on Podman instead of Docker.
- How do I install foxws/laravel-podman in a Laravel project?
- Install the package with Composer using the foxws/laravel-podman package name, then publish its configuration in your Laravel application. Confirm that Podman is available on the host and choose the preset that matches your host provisioning method, such as lpod or laravel-installer. Test the setup in a staging environment before rolling it out.
- Which Laravel and PHP versions does laravel-podman support?
- The provided context does not list exact Laravel and PHP version constraints for foxws/laravel-podman. Check the repository composer.json and release notes for the supported Laravel and PHP ranges before installing or upgrading. The 6.0.1 release is described as a backward-compatible patch from 6.0.0, but you should still verify your application version.
- What Podman version do I need for Laravel Podman?
- The context does not state a minimum required Podman version. Because the package relies on Podman Quadlet support and socket behavior such as ondemand.socket, verify those features on your host Podman version. Run a staging test with your intended Podman release before production.
- How does the ondemand preset work for Laravel queue workers?
- The ondemand preset is intended for demand-based scaling of Laravel queue workers in Podman-backed environments. In version 6.0.1, the idle check only runs while the application's ondemand.socket is active, which helps avoid stopping workers when the socket is not running. This behavior is important for worker lifecycle reliability under changing load.
- What changed in foxws/laravel-podman 6.0.1?
- Version 6.0.1 is a patch release that fixes idle-check behavior and reduces spurious error logs. It stops logging errors for workers the application does not have and aligns the idle check with lpod idle behavior. The idle check now only runs while the app's ondemand.socket is active, and the release is described as backward-compatible from 6.0.0.
- Do I need lpod or laravel-installer to use laravel-podman?
- The release notes reference both lpod and laravel-installer, and the ondemand preset is retained for hosts without lpod. Your choice depends on how the host is provisioned and whether lpod is available in that environment. Confirm the currently supported path in the package documentation before standardizing on one method.
- Is the ondemand preset production-ready for high-throughput Laravel workloads?
- The ondemand preset supports demand-based worker scaling, but the provided context does not include high-throughput benchmarks or production guarantees. The 6.0.1 idle-check fix should improve reliability by limiting idle checks to active ondemand.socket conditions. Validate scaling, worker stops, and log noise in a staging environment that resembles production load.
- How do I test laravel-podman worker scaling and idle checks before production?
- Set up a staging host with Podman, install and configure the package, and select the preset that matches your provisioning method. Simulate queue load and verify that workers start and stop as expected, especially that idle checks run only while ondemand.socket is active. Monitor logs for missing-worker errors and unexpected worker termination before promoting the change.
- What are alternatives to laravel-podman for containerized Laravel deployments?
- The package is specifically for teams using Podman with Laravel, so Docker-based Laravel tooling is the natural alternative if you are not standardizing on Podman. Within Podman setups, compare the lpod and laravel-installer provisioning paths and the available presets for queue worker management. Evaluate alternatives against your need for demand-based worker scaling and Quadlet support.