Download the PHP package shippercli/cli without Composer

On this page you can find all versions of the php package shippercli/cli. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package cli

Shipper CLI

CI PHPStan PHP

Declarative application deployments through a built-in provider and Composer provider plugins.

Shipper reads shipper.yml, validates the selected project and profile, shows the planned operations, and delegates deployment work to the installed provider package.

Install

Install globally with Composer:

Deployment Features

Or work from source:

Prebuilt PHAR binaries are published on the releases page.

Providers

Provider availability and lifecycle support currently differ by distribution:

Provider Distribution Registered Validate / plan Apply Destroy Status / logs / rollback
Ploi shippercli/provider-ploi Composer plugin When installed Yes Yes Yes Status and logs; no rollback
cPanel shippercli/provider-cpanel Composer plugin When installed Yes Yes Yes Yes
Forge, Railway, Cloudflare Pages, Hostinger, Coolify, EasyPanel, Portainer Experimental source only No Experimental Unavailable Unavailable No

Incomplete in-tree providers are deliberately not registered. Calling an unimplemented lifecycle operation directly returns failure with a clear not implemented error rather than reporting a successful deployment.

For local global use, install the CLI and providers into the same Composer home, then run Composer's global vendor/bin/shipper:

Shipper discovers packages with Composer's runtime plugin metadata. Provider credentials, platform features, and configuration options belong to each provider's documentation rather than the core CLI.

The release PHAR has its own dependencies and cannot discover separately installed provider packages. For CI, use shippercli/actions/.github/actions/shipper@c2c276e12f831ba2c3377a063d579fede5cc5ecc, which installs the CLI and providers together in an isolated Composer directory.

Configure

Create shipper.yml in the application repository:

provider_name is the slug registered by the installed package. Profiles can override provider-supported runtime, database, domain, environment, and lifecycle options.

Environment placeholders use ${NAME} syntax and are resolved at runtime. Keep credentials in the shell, CI secrets, or another secret manager.

Commands

status, logs, and rollback are optional provider capabilities. Shipper returns a clear error when the selected provider does not implement one.

Provider contracts

Every provider implements validation, planning, apply, destroy, name, and error-reporting methods from shippercli/contracts.

Optional contracts add:

The CLI adapts installed contract providers to its internal flows. New providers are Composer plugins and are discovered from their package metadata.

GitHub Actions

A minimal deployment workflow installs Shipper and its provider packages in an isolated tool directory through the composite action:

See GitHub Actions for production, staging, preview, cleanup, and reusable-action patterns.

Documentation

The codebase targets PHP 8.3+, Laravel Pint, PHPStan level 9, and Pest.

Release

Tags build and publish the PHAR through GitHub Actions:

License

MIT

All versions of cli with dependencies

PHP Build Version
Package Version
Requires composer-runtime-api Version ^2.2
php Version ^8.3
guzzlehttp/guzzle Version ^7.0
laravel-zero/framework Version ^12.1
laravel/forge-sdk Version ^3.25
ploi/ploi-php-sdk Version ^1.9
shippercli/contracts Version ^1.0
symfony/clock Version ^7.3
symfony/console Version ^7.3
symfony/string Version ^7.3
symfony/translation Version ^7.3
symfony/yaml Version ^7.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package shippercli/cli contains the following files

Loading the files please wait ...