- Is philetaylor/akeeba a Laravel package?
- No. It is a Symfony 3+ bundle that wraps the Akeeba Backup API, and it ships a Bundle class, a DI extension, a configuration tree, and Symfony-flavored service wiring that Laravel's container does not consume. Treat it as prior art or a reference implementation for the HTTP contract, not as a Laravel dependency.
- Can I install philetaylor/akeeba in a Laravel application?
- Composer may install it, but it will not work idiomatically in Laravel because the Symfony bundle machinery is not consumed by Laravel's container. Adoption is off the table for a Laravel codebase; extract the endpoint and payload knowledge instead. Build a small in-stack client behind an interface and bind it in a service provider.
- What does philetaylor/akeeba actually do?
- It is a thin Symfony bundle for interacting with the Akeeba Backup JSON API using configurable host, API key, and secret values. It provides a Guzzle-backed client with a handful of endpoint methods and tools for working with Akeeba-generated .jpa backup archives. The integration surface is HTTP, so the knowledge is portable even though the wrapper is Symfony-specific.
- What are the requirements to use the Akeeba Backup API?
- You need Akeeba Backup Professional because the JSON API is not a free-tier feature. You also need the API enabled, a provisioned secret, and network reachability from your application tier to the Joomla or WordPress host. That makes it a procurement and network workstream, not just a code task.
- Which Symfony and PHP versions does philetaylor/akeeba support?
- The package targets the Symfony 3/4 era, and Symfony 3 reached end-of-life in November 2018. Its version constraints likely pin EOL PHP, Symfony, and Guzzle versions, which conflicts with any supported-runtime policy. It is not suitable for modern Symfony 5.4+, 6, or 7 without a rewrite.
- Is philetaylor/akeeba maintained and safe for production?
- Health signals are uniformly negative: zero stars, zero dependents, a single maintainer in a personal namespace, and no visible community or CI signal. There is no security disclosure path, no CVE feed, and no release cadence. That makes it a poor fit for production, especially at security review.
- How do I integrate Akeeba Backup with Laravel?
- Do not install the Symfony bundle in Laravel. Build an AkeebaClient behind an interface, bind it in a service provider, expose configuration via config/akeeba.php and environment variables, and use Laravel's HTTP client or Guzzle directly. Do not import Symfony components to bridge the gap.
- How long does it take to reimplement the Akeeba Backup client in Laravel?
- The reusable asset is only a few hundred lines of HTTP client and DTO logic, so reimplementation is estimated at three to eight engineer-days including tests. That is far more bounded than adopting and maintaining an abandoned dependency. Start from the repository as a specification source for endpoints and payloads.
- What is the difference between observe-only and acting with Akeeba Backup?
- Observe-only work covers inventory, backup freshness, and download metadata, and it is low risk. Acting covers triggering backups and restoring, where restore is destructive and should be out of scope for a first version. The bundle shows no evidence of handling Akeeba's long-running step-based flow, lock files, or secret rotation.
- Are there alternatives to philetaylor/akeeba for Akeeba Backup integration?
- Check vendor-supported paths first: Akeeba Remote CLI, akeeba:backup, and cron plus post-processing may satisfy the requirement without custom code. If not, use this repository as prior art and build a small in-house client in your target stack. For Laravel, that means an HTTP client behind an interface, not a Symfony bundle.