- Can I use Artisan Deployer for Laravel 6+ or 8+ projects?
- No, this package explicitly supports Laravel 5.x only. Upgrading to newer Laravel versions would require a fork or alternative tools like Deployer.php or Laravel Forge, which support modern Laravel releases.
- How do I install Artisan Deployer in my Laravel project?
- Run `composer require bencagri/artisan-deployer` in your project root. No additional setup is needed beyond defining your deployment logic in a PHP file, which integrates directly with Artisan commands.
- Does Artisan Deployer support zero-downtime deployments?
- Yes, it includes zero-downtime strategies for Laravel 5.x applications. You define the process in PHP, such as syncing files while keeping the old version running until the new one is ready.
- Will this work with GitLab CI or GitHub Actions?
- Yes, you can trigger deployments via CI/CD pipelines by running `php artisan deploy` as a pipeline step. However, ensure your CI environment has SSH access to your servers and PHP 7.1+ installed.
- Is Artisan Deployer suitable for multi-server deployments?
- Absolutely. The package supports multi-server deployments by defining each server’s SSH credentials and deployment steps in your PHP configuration file, making it ideal for staging/production setups.
- What if I need rollback capabilities or advanced deployment features?
- Artisan Deployer lacks built-in rollback or advanced features like canary releases. For these, consider alternatives like Deployer.php or Laravel Forge, which offer more comprehensive DevOps tooling.
- Does this package work with Docker or Kubernetes?
- No, Artisan Deployer is designed for traditional SSH-based deployments to non-containerized environments. For Docker/Kubernetes, use tools like Docker Compose, ArgoCD, or Spinnaker instead.
- How do I configure environment-specific deployments (e.g., staging vs. production)?
- Define separate deployment stages in your PHP config file using different SSH credentials and paths. You can then trigger deployments with `php artisan deploy:stage` or similar commands.
- Are there any security risks using an archived package?
- Yes, since development is inactive, there’s a risk of unpatched vulnerabilities in dependencies. Audit your Composer dependencies (`composer why-not`) and consider forking or migrating to an actively maintained alternative.
- Can I use Artisan Deployer for non-Laravel PHP projects?
- Technically possible but not ideal. The package is tightly coupled with Laravel’s Artisan CLI. You’d need to mock Laravel’s container or rewrite parts of the logic, which may not be worth the effort for non-Laravel projects.