Weave Code
Symfony Client Laravel Package
1pilotapp/symfony-client
1Pilot Symfony Client integrates your Symfony app with the 1Pilot dashboard for centralized monitoring and management. Track uptime and SSL, detect config and server changes, manage Composer packages, and receive alerts via email, Slack, or Discord.
1Pilot.io, a universal dashboard to effortlessly manage all your Symfony applications
Frequently asked questions about Symfony Client
- Can I use 1Pilot Symfony Client directly in a Laravel app without Symfony components?
- No, this package is designed for Symfony apps. For Laravel, you’d need to deploy it as a separate Symfony microservice (e.g., Docker container) and communicate via Laravel’s HTTP client or API. Direct Composer installation risks breaking Laravel’s autoloader.
- What Laravel versions support integration with this package?
- Laravel 8+ is recommended due to Symfony 7’s PHP 8+ requirements. Legacy Laravel (pre-8) is unsupported. Check your app’s `composer.json` for Symfony component compatibility (e.g., `symfony/http-client`).
- How do I securely store the ONE_PILOT_PRIVATE_KEY in Laravel?
- Use Laravel’s `.env` file or a secrets manager like HashiCorp Vault. Avoid hardcoding. For production, rotate keys periodically and restrict access to the environment variable. Example: `ONE_PILOT_PRIVATE_KEY=your_key_here` in `.env`.
- Will this package conflict with Laravel’s built-in monitoring tools?
- Potential conflicts exist if your Laravel app uses Symfony components (e.g., `symfony/process`). Run `composer why symfony/process` to audit dependencies. For pure Laravel, deploy 1Pilot as a sidecar service to avoid routing or container clashes.
- How do I integrate this with Laravel’s queue system (e.g., Horizon)?
- If using Symfony’s `Process` component, run the 1Pilot client in a Laravel background job via `symfony/process`. For pure Laravel, wrap the client in a Docker container and poll its metrics via HTTP. Avoid mixing Symfony’s Process with Laravel’s queues directly.
- Does this package support Laravel’s mail system (Swiftmailer or Symfony Mailer)?
- No, the package uses Symfony’s native mail system. If your Laravel app uses Swiftmailer, configure 1Pilot’s email alerts via its dashboard or proxy emails through Laravel’s mail queue with a custom transport.
- What’s the best way to monitor a Laravel app with this package if I don’t use Symfony?
- Deploy the Symfony client as a Docker container alongside Laravel. Use Laravel’s HTTP client to poll the container’s `/health` or `/metrics` endpoints. This avoids dependency conflicts and keeps monitoring isolated.
- Are there Laravel-native alternatives to this package?
- Yes, consider `spatie/laravel-monitoring` for Laravel-specific uptime/health checks or `laravel-debugbar/debugbar` for config/environment monitoring. For Composer package tracking, `composer-outdated` or `roave/security-advisories` are lightweight alternatives.
- How do I test this package in a Laravel CI pipeline?
- For Symfony-integrated Laravel apps, test the package’s routes (e.g., `/one_pilot/health`) via HTTP requests in PHPUnit. For Docker deployments, mock the container’s API responses. Verify `.env` variables are loaded and alerts trigger correctly.
- What performance impact does this package have on Laravel apps?
- Minimal if deployed as a sidecar. Direct integration may add ~50–200ms latency per monitoring check due to HTTP callbacks to 1Pilot’s servers. Test API response times and background job execution under load. Avoid running checks during peak traffic.
Weaver
How can I help you explore Laravel packages today?