- What is tzurbaev/laravel-forge-api used for?
- It is a Laravel-oriented PHP SDK that wraps the Laravel Forge REST API in a fluent interface. It lets PHP applications list and manage Forge resources such as servers, sites, deployments, and workers. Use it for internal admin tools, provisioning dashboards, or deployment automation, ideally behind an application-owned service boundary.
- How do I install tzurbaev/laravel-forge-api in a Laravel app?
- Install it with Composer using the package name tzurbaev/laravel-forge-api. Then verify the package’s service provider, facade, and configuration publishing behavior against its composer.json and source because the package is archived. Run a small read-only test before integrating it broadly.
- Which Laravel and PHP versions are supported by laravel-forge-api?
- The supported versions are defined by the package’s Composer constraints, not by current Laravel documentation. Because the last release was in January 2021, you must audit composer.json against your target PHP and Laravel versions. Expect compatibility work for newer Laravel and HTTP client dependencies.
- Is tzurbaev/laravel-forge-api still maintained?
- No, the repository is archived and the last release was in January 2021. That means no upstream fixes for Laravel/PHP compatibility, security issues, Guzzle changes, or Forge API evolution. The integrating team owns maintenance, forking, or replacement.
- Can this package manage Forge servers, sites, deployments, and workers?
- The package is described as wrapping the Laravel Forge API for servers, sites, deployments, workers, and other Forge resources. However, its endpoint coverage should be checked against current Forge API documentation before relying on specific actions. Confirm both read-only and mutating operations in a non-production account.
- How should I store and use Laravel Forge API tokens with this package?
- Forge API tokens are high-privilege credentials, so store them in environment variables or a secrets manager rather than in code. Add scoping where possible, audit logging, and rotation procedures in the integrating application. The archived package does not remove your responsibility for token security.
- Does laravel-forge-api handle current Forge API pagination, rate limits, and error responses?
- That cannot be assumed for an archived package last released in 2021. Audit the HTTP layer and add contract tests with mocked responses for success, auth failure, rate limit, validation error, and partial failure. Put retries, backoff, and error normalization in your own adapter.
- How can I test a laravel-forge-api integration without affecting production Forge resources?
- Start with a read-only proof of concept against a non-production Forge account to list servers, sites, and deployments. Use mocked HTTP responses and contract tests so API changes are detected before runtime. Gate any mutating operations behind approvals and idempotency controls.
- Should I use tzurbaev/laravel-forge-api in production?
- Treat it as a reference implementation or short-term accelerator, not a strategic dependency. If it materially reduces discovery effort, wrap it in an internal adapter, pin the version, and plan to replace it with a thin first-party client using Laravel’s HTTP client. The archived status creates high lifecycle risk.
- What is the best alternative or migration path from laravel-forge-api?
- Build a small first-party Forge client around Laravel’s HTTP client once you understand required endpoints and error semantics. Put the package behind an internal ForgeClient or ForgeService interface so callers do not depend on it directly. If needed, maintain a fork or vendor the package temporarily while migrating.