Weave Code
Forge Cli Laravel Package
laravel/forge-cli
Command-line interface for Laravel Forge to provision and manage servers, deploy sites, and handle common tasks like SSL certificates, scheduled jobs, and queue workers—bringing Forge’s dashboard capabilities to your terminal.
The Laravel Forge CLI.
Frequently asked questions about Forge Cli
- How do I install Laravel Forge CLI for Laravel projects?
- Run `composer global require laravel/forge-cli` to install globally, then authenticate with `forge login` using your Forge API key. Ensure your Laravel project’s `composer.json` includes Forge CLI as a dev dependency if needed for CI/CD scripts.
- Does Laravel Forge CLI support Laravel 10 and PHP 8.3?
- Yes, Forge CLI supports Laravel 10 and PHP 8.3 out of the box. The CLI aligns with Forge’s latest server recipes, which include optimized configurations for modern Laravel and PHP versions. Verify compatibility by checking Forge’s [official docs](https://forge.laravel.com/docs/1.0/cli.html).
- Can I use Forge CLI to provision servers without a Laravel Forge subscription?
- No, Forge CLI requires an active Laravel Forge subscription. The CLI is a command-line interface for Forge’s API, so you’ll need to purchase a Forge plan to provision servers, deploy sites, or manage configurations. Free trials may be available via Forge’s website.
- How do I automate Laravel deployments with Forge CLI in GitHub Actions?
- Add `forge deploy` to your GitHub Actions workflow under a `deploy` job. Use environment variables for Forge API keys and server IDs. Example: `forge deploy --server=123 --remote=production`. Ensure your workflow has permissions to access Forge’s API via the stored secrets.
- What’s the difference between Forge CLI and Laravel Envoyer?
- Forge CLI focuses on server provisioning, configuration, and deployment management (e.g., Nginx, PHP, SSL), while Envoyer is a dedicated zero-downtime deployment service. Use Forge CLI for infrastructure-as-code and Envoyer for deployment pipelines. Some teams combine both for full-stack automation.
- How do I handle SSL certificates with Forge CLI?
- Use `forge ssl:create` to provision Let’s Encrypt SSL certificates for your domain. The CLI automates certificate issuance, renewal, and Nginx configuration. For wildcard certificates, specify `--wildcard` and ensure DNS validation is configured in Forge’s dashboard.
- Can Forge CLI manage queue workers and scheduled jobs?
- Yes, Forge CLI supports managing queue workers (`forge queue:start`) and scheduled jobs (`forge schedule:run`). These commands integrate with Forge’s server recipes to ensure proper Supervisor or systemd configurations for Laravel’s queue and task scheduling.
- Is Forge CLI suitable for Kubernetes or Docker-based Laravel deployments?
- No, Forge CLI is designed for traditional server provisioning (e.g., DigitalOcean, AWS) and lacks native Kubernetes or Docker support. For containerized Laravel apps, consider tools like Docker Compose, Kubernetes manifests, or Laravel Sail instead.
- How do I troubleshoot Forge CLI connection errors?
- Verify your Forge API key (`forge auth:key`) and server provider credentials. Check network connectivity to Forge’s API endpoints. Run `forge debug` for detailed logs. If issues persist, consult Forge’s [CLI documentation](https://forge.laravel.com/docs/1.0/cli.html#troubleshooting).
- What alternatives exist if I don’t want to use Forge CLI?
- Alternatives include Terraform (for IaC), Ansible (for configuration management), or self-hosted tools like RunCloud or ServerPilot. For Laravel-specific deployments, consider Envoyer or Deployer. Choose based on your need for cloud agnosticism, cost, or Laravel integration.
Weaver
How can I help you explore Laravel packages today?