Laravel Podman Laravel Package

Product Decisions This Supports

• Build vs. buy for container/worker tooling. This package is a maintained integration between Laravel and Podman (the rootless, daemonless container engine). Choosing it is a decision to buy a supported integration rather than hand-rolling worker/container lifecycle scripts. The 6.0.1 patch shows the ondemand preset is actively maintained — relevant when weighing a community dependency against bespoke automation.
• Roadmap: idle-aware queue workers. The ondemand preset starts workers on demand and stops idle ones; 6.0.1 scopes the idle check to an active ondemand.socket and stops only the workers that actually exist. That directly supports a cost-reduction roadmap item for idle queue infrastructure.
• Deployment target / hosting strategy. Release notes explicitly keep the ondemand preset for "hosts set up without lpod, such as apps installed with laravel-installer." This signals support for heterogeneous hosting (with and without the lpod CLI), which affects deployment and onboarding decisions.
• Platform fit and lock-in. Podman is OSS, rootless and daemonless — a strategic alternative to Docker for security-constrained or enterprise-Linux environments. Adopting this package supports a rootless deployment direction without custom orchestration.
• Use cases: Podman-based local/dev parity, containerized queue workers, on-demand worker lifecycle to save idle compute, and apps provisioned via laravel-installer on hosts lacking lpod.

When to Consider This Package

Consider adopting when:

• Your infrastructure standardizes on Podman (rootless/daemonless requirements, RHEL/Fedora-style environments) rather than Docker.
• You want on-demand, idle-stopping queue workers and the ondemand preset matches your operational model.
• You support laravel-installer / no-lpod hosts — this release explicitly preserves that path.
• You prefer a maintained package over a custom worker-management script.

Look elsewhere when:

• You are on Docker, Laravel Sail, Kubernetes, or a managed container platform — the value here is Podman-specific.
• You use managed queue services (SQS, managed Redis) where worker lifecycle is handled for you.
• You require enterprise SLAs or guaranteed long-term support — this is a community package with 6.x patch releases from individual contributors.

How to Pitch It (Stakeholders)

Executives: A small, actively maintained open-source integration that runs Laravel queue workers in Podman containers with idle-aware shutdown — a direct lever on idle infrastructure cost and a path to rootless, vendor-neutral container hosting. Patch-level maintenance and backward-compatible fixes keep adoption risk low.

Engineering: Drop-in Laravel/Podman integration with an ondemand preset. 6.0.1 tightens the idle check (runs only while ondemand.socket is active, no false errors for workers the app doesn't have) and keeps the no-lpod / laravel-installer host path working. This is a patch release with no breaking changes — safe to adopt or upgrade.