Weave Code
Cli Laravel Package
shippercli/cli
Shipper CLI is a command-line toolkit for Laravel and PHP projects, giving developers a fast, scriptable way to run common shipping, build, and deployment tasks from the terminal with simple, consistent commands.
At a glance
Frequently asked questions about Cli
- What is Shipper CLI and what does it do for Laravel projects?
- Shipper CLI is a command-line toolkit for Laravel and PHP projects that provides fast, scriptable commands for common shipping, build, and deployment tasks. It runs from the terminal and is intended for pipeline or deployment work rather than inside your application runtime. It is not a Composer library you require into vendor, so it does not couple to your app's service container or framework version.
- How do I install Shipper CLI for a Laravel project?
- With v1.0.3 you install it as a standalone executable rather than a Composer package: download the release artifact, make it executable with chmod +x, and run ./shipper --version to confirm it works. Then invoke it from a CI job or deployment script. Check the release checksum and provenance before execution, and consult the README for exact artifact names.
- Does Shipper CLI work with Laravel 10 and Laravel 11?
- Shipper CLI is designed as a pipeline-layer tool for Laravel and PHP projects and does not appear in composer.json, so it does not raise your app's PHP version floor or affect autoloading. Because it sits outside the application runtime, Laravel version coupling should be minimal. Still, confirm the CLI's documented PHP and Laravel support in the README before adopting it.
- Is Shipper CLI a Composer package or a standalone binary?
- In v1.0.3 Shipper CLI moved to a standalone, downloadable executable and the release explicitly exposes the Composer CLI binary; the earlier v1.0.2 route was a Composer-installed binary. The standalone approach decouples the deploy tool from your application's composer.json and lockfile, so you can version and upgrade it independently. Pin the release by digest rather than relying on a mutable tag.
- Which OS and CPU architectures does Shipper CLI support?
- The release notes cited in the assessment do not enumerate the supported OS and architecture matrix, so Linux versus macOS and amd64 versus arm64 support must be confirmed. Standalone binaries often imply per-platform artifacts, and an unsupported CI runner architecture such as arm64 or Alpine/musl could block adoption. Verify the published artifacts and attestations for your runner before wiring it into CI.
- How do I verify the Shipper CLI binary before running it in CI?
- The release publishes a SHA-256 checksum and GitHub build provenance, so you can wire checksum verification plus gh attestation verify into CI as a gate before execution. Confirm that the provenance is generated by a GitHub Actions workflow in the shippercli/cli repository and pin the artifact by digest, not by the v1.0.3 tag. This mitigates but does not eliminate supply-chain risk from a self-executing binary.
- Can I test Shipper CLI commands locally before using them in production?
- Yes, you can download the artifact, make it executable, and run ./shipper --version or individual commands on a local machine or in a scratch CI job before using it against production. The assessment recommends a greenfield pilot in a single non-production environment first. Test credentials and target-host prerequisites locally, since the README details were not included in the assessment.
- Can Shipper CLI run alongside an existing deployment pipeline?
- This is an open architectural question: the CLI may expect to own the release lifecycle end to end, including build, release directory, and symlink switch, or it may be scoped to a single pipeline stage. The assessment recommends confirming whether it is additive or a replacement architecture before adoption. A pilot in one non-production environment is the safest way to determine this.
- Does Shipper CLI need root privileges or specific hosting support?
- The assessment could not confirm whether Shipper CLI requires root or elevated privileges on target hosts, or whether it can run as the deploy user. It also could not confirm target-host prerequisites, required credentials such as SSH keys or deploy tokens, or support for managed PaaS, bare VM, and container topologies. Review the README and test against your hosting setup before production use.
- Who maintains Shipper CLI and what are the production risks?
- Shipper CLI is a single-maintainer project by @marktopper, so the dominant long-term risk is a small bus factor rather than the code itself. Supply-chain risk is medium because a downloaded, self-executing binary enters CI and production hosts, which checksums and provenance mitigate but do not eliminate. Pin by digest, keep the v1.0.2 Composer-binary route as a fallback, and confirm support response expectations.
Weaver
How can I help you explore Laravel packages today?