- Is gpenverne/cloudflare-bundle a Laravel package?
- No. It is a Symfony bundle built around a Bundle subclass, a DependencyInjection Extension and a Configuration tree, none of which Laravel's service container reads. Installing it into a Laravel app will not give you working services. Treat it as a reference implementation for wiring the Cloudflare SDK, not as a dependency to adopt.
- Can I install gpenverne/cloudflare-bundle with Composer in a Laravel app?
- You can run composer require, but its Symfony, Guzzle and PHP constraints were written for the PHP 7.x and Symfony 3/4 era, so resolution on Laravel 10 or 11 often fails or needs --ignore-platform-reqs. Even when it installs, Laravel never loads the bundle extension or registers its services. The practical path is to depend on cloudflare/cloudflare-php directly and write a small service provider.
- Does this bundle support Laravel 9, 10 or 11?
- No. It ships no Laravel service provider, facade or publishable config, and its last release was January 2020, well before Laravel 9. Its Symfony and Guzzle constraints conflict with the Guzzle 7 and PHP 8.1+ baseline those Laravel versions expect. Assume zero official Laravel support and plan accordingly.
- Which Cloudflare SDK and credential model does cloudflare-bundle use?
- The 2020 release predates Cloudflare SDK v2 and v3, which moved from email plus global API key to scoped API tokens. Depending on the pinned cloudflare/sdk constraint, you may be adopting a credential model you should not use in production. Check the package's composer.json before assuming token support, and prefer the current token-based SDK for new code.
- How do I purge Cloudflare cache by URL, tag or zone in Laravel?
- The bundle exposes purge operations as Symfony services, so in Laravel you would recreate that wiring: bind a configured Guzzle adapter as a singleton, register the Zones and cache endpoint classes, then call the purge methods from a controller, job or Artisan command. Purging by URL, tag or the whole zone is only a handful of SDK calls and does not require the bundle. Its configuration tree is still useful as a starting schema for config/cloudflare.php.
- How do I configure Cloudflare credentials for this bundle?
- In Symfony you would put credentials in YAML and let the extension build the adapter. The Laravel equivalent is a config/cloudflare.php file plus environment variables such as CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID, read through config() and never echoed in exception handlers or config:cache output. Scope the token to only the zones and permissions you actually need.
- Is gpenverne/cloudflare-bundle maintained and safe for production?
- The signals are weak: around 2 stars, 0 dependents, a single maintainer and no release since January 2020. There is no visible security advisory history or disclosure process, and the package handles API credentials. For production, prefer the maintained Cloudflare SDK behind your own thin wrapper so you control updates, credentials and secret handling.
- What are the Laravel alternatives to this Symfony bundle?
- There is no widely adopted Laravel-native Cloudflare package, so most teams write an 80 to 150 line App\Providers\CloudflareServiceProvider over cloudflare/cloudflare-php. That gives you a configured Guzzle adapter with timeouts and retry middleware as a singleton, endpoint bindings for zones and DNS, and a published config file. It is cheaper to own than an abandoned Symfony bundle.
- How do I test Cloudflare integration in Laravel without hitting the live API?
- Use Guzzle's MockHandler with your adapter, or Laravel's Http::fake if you bypass the SDK and call the REST endpoints directly. Assert request paths, methods and bodies for purge and DNS calls, and keep real credentials out of CI. The bundle ships no testing helpers you can reuse, so the mocks live in your own test suite.
- Do I need this bundle to manage Cloudflare zones and DNS records?
- No. Zone lookup and DNS record CRUD are a small number of SDK calls, so a lightweight in-house wrapper is usually sufficient. Copy the bundle's DependencyInjection Configuration class as documentation for the settings you need, then build on the current SDK. That also avoids dragging symfony/framework-bundle into a Laravel application.