Download the PHP package sydgren/laravel-shipit without Composer
On this page you can find all versions of the php package sydgren/laravel-shipit. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download sydgren/laravel-shipit
More information about sydgren/laravel-shipit
Files in sydgren/laravel-shipit
Package laravel-shipit
Short Description Trigger and monitor ShipIt deployments from Artisan — php artisan shipit:deploy.
License MIT
Homepage https://shipit.henriknordquist.dk
FAQ
Example:
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 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.
Informations about the package laravel-shipit
ShipIt Deployer
Trigger and monitor ShipIt deployments straight from your Laravel app's Artisan console.
Drop it into any Laravel project, point it at a ShipIt site, and deploy from your terminal or CI pipeline — --watch streams the live log and exits non-zero if the deployment fails, so it gates a pipeline cleanly.
Requirements
- PHP 8.2+
- Laravel 11, 12, or 13
Installation
The service provider is auto-discovered. Optionally publish the config:
Configuration
Configure via environment variables (no published config needed):
Create a token in ShipIt under Settings → API tokens. SHIPIT_SITE is the
default site every command targets when you don't pass one explicitly — set it
once per project and php artisan shipit:deploy just works.
Commands
| Command | Description |
|---|---|
shipit:deploy {site?} {--branch=} {--watch} {--no-wait} |
Trigger a deployment |
shipit:status {site?} |
Latest deployment status for a site |
shipit:logs {deployment?} {--site=} {--watch} |
Show / follow deployment output |
shipit:deployments {site?} {--limit=10} |
List recent deployments |
shipit:rollback {deployment} |
Roll back to a previous successful deployment |
shipit:sites |
List all sites on your account (handy for finding ids) |
shipit:script {site?} {--check} {--force} {--print} |
Scaffold or validate .shipit/deploy.yml |
{site} accepts either a numeric ShipIt id or a domain/name. When omitted,
commands fall back to SHIPIT_SITE.
Examples
Deployment steps in the repository
By default a site's deployment steps are configured in ShipIt. Commit a
.shipit/deploy.yml and the repository takes over instead — the steps are then
versioned and reviewed with the code they deploy.
Steps run in order, in the new release directory, before the symlink switches.
critical defaults to true here — a failing step stops the deployment
unless you say otherwise. enabled: false keeps a step in the file without
running it. The same {RELEASE_PATH}, {SHARED_PATH}, {BASE_PATH},
{PREVIOUS_RELEASE}, {BRANCH}, {COMMIT}, {COMMIT_SHORT}, {DOMAIN} and
{PHP_VERSION} variables are available as in the UI.
ShipIt validates the file again when it deploys, and a malformed file fails the deployment rather than silently falling back to the site's own steps.
In CI (GitHub Actions)
Validate a committed deployment script on every pull request:
Programmatic use
The ShipIt facade exposes the same API client the commands use:
Testing
License
MIT
All versions of laravel-shipit with dependencies
guzzlehttp/guzzle Version ^7.8
illuminate/console Version ^11.0|^12.0|^13.0
illuminate/http Version ^11.0|^12.0|^13.0
illuminate/support Version ^11.0|^12.0|^13.0