Weave Code
Provider Cpanel Laravel Package
shippercli/provider-cpanel
cPanel deployment provider for Shipper CLI, letting Laravel and PHP projects ship straight to cPanel hosting. Automates uploads, file placement, and release steps through Shipper's provider pipeline so you can deploy without SSH or manual FTP work.
At a glance
Frequently asked questions about Provider Cpanel
- How do I install shippercli/provider-cpanel with Composer?
- Install it as a Composer dependency in the same project where Shipper CLI is already set up, using composer require shippercli/provider-cpanel. Because it is a provider for Shipper CLI rather than a standalone deployer, Shipper should already be installed and configured for your Laravel or PHP application. After installation, register or select the cPanel provider in your Shipper deployment configuration.
- Does this package work on cPanel shared hosting without SSH access?
- Yes. The provider was built for shared and managed cPanel environments, so it does not require SSH or manual FTP work to publish a release. Shipper drives the deployment through its provider pipeline, and the cPanel provider handles the automated uploads and file placement for you.
- Which Laravel and PHP versions does shippercli/provider-cpanel support?
- The package overview does not publish a specific Laravel or PHP version matrix. Check the require and require-dev constraints in the package's composer.json, and confirm the supported PHP range for the Shipper CLI version you are running. If your application targets an older Laravel release, verify compatibility before adding it to a production pipeline.
- How do I configure cPanel hosting credentials and the remote deploy path?
- The provider exposes configurable remote paths and hosting credentials, which you set in your Shipper deployment configuration for the cPanel target. Point the remote path at the correct document root or application directory on the hosting account, such as the directory behind your domain or subdomain. Keep credentials out of version control by supplying them through environment variables or your CI secrets store rather than committing them to the repository.
- Can I deploy a Laravel application to a shared cPanel account with this provider?
- Yes, that is the primary use case. The provider adds cPanel deployment support to Shipper CLI so Laravel and PHP projects can be shipped to shared or managed cPanel hosting consistently. You get automated file uploads and release handling instead of maintaining your own deployment scripts.
- How does the provider handle releases and repeatable deployments?
- It plugs into Shipper's provider pipeline, so each deployment follows the same defined steps: uploading build files and placing them at the configured remote path. That makes releases repeatable across environments because the sequence lives in configuration rather than in ad hoc FTP sessions or one-off shell scripts. Running the same pipeline again produces the same result on the hosting account.
- Is shippercli/provider-cpanel a replacement for custom FTP scripts or tools like Deployer?
- It replaces the manual side of cPanel deployments, so you no longer need hand-written FTP scripts or shell tooling that requires SSH. If you already run Shipper CLI for other targets, adding cPanel support keeps all environments in one workflow. For hosts with full SSH and process control, SSH-based deployers may still offer more flexibility, but they are not required here.
- How should I test a cPanel deployment before pushing to production?
- Create a staging subdomain or a separate cPanel account and point a test deployment at its own remote path, then run your Shipper pipeline against it first. Verify that uploaded files land in the right directory, that permissions and ownership allow the web server to read them, and that the application boots without errors. Only promote the same configuration to your production target once the staging release succeeds.
- What production concerns come with deploying Laravel to cPanel through this provider?
- Shared cPanel accounts usually restrict long-running processes, custom PHP binaries, and some file operations, so plan around those limits. After each release, make sure writable directories such as storage and the cache paths have correct permissions, and clear or rebuild configuration and view caches as part of your process. If you run queues or scheduled tasks, confirm your host supports them, since shared hosting often relies on cron entries rather than persistent workers.
- Is shippercli/provider-cpanel actively maintained, and where do I report issues?
- The package listing does not expose a public repository URL, so check Packagist for the latest release date and version history to gauge activity. Review the release notes before upgrading, particularly if you pin a Shipper CLI version in CI. For bugs or feature requests, use the issue tracker linked from the package's Packagist page once it is published.
Weaver
How can I help you explore Laravel packages today?