Weave Code
Cloud Flare Bundle Laravel Package
happyr/cloud-flare-bundle
Symfony bundle for integrating Cloudflare into your application. It provides configuration and services for the Cloudflare API, helping you manage zones and purge cached content so your Symfony app can automate cache invalidation and keep content fresh through a simple, configurable service layer.
At a glance
Frequently asked questions about Cloud Flare Bundle
- Is happyr/cloud-flare-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. It ships a Bundle class, a DI extension that compiles a configuration tree, and YAML/XML service definitions. Laravel never executes that plumbing, so inside a Laravel app the package behaves as an inert class library.
- Can I install happyr/cloud-flare-bundle in a Laravel application?
- You can run composer require, but none of the Symfony-specific wiring will execute: there is no service provider, no facade, and no publishable config. You would end up hand-wiring credentials, container bindings, and the purge trigger yourself, which is roughly the same effort as writing the integration from scratch.
- Does this package support Laravel 10 or 11 and PHP 8.2?
- Unlikely. The bundle predates Laravel 10/11 and PHP 8.2, and its Symfony and Cloudflare SDK constraints were pinned at authoring time. Even where Composer resolves the dependency, you get no Laravel-native features, so version support is not really the blocker.
- How do I purge Cloudflare cache from Laravel?
- Use the official Cloudflare PHP SDK inside a small Laravel service class, bind it in a service provider, and call the purge endpoint from a queued job. Purge is fire-and-forget by nature, so add retries, logging, and an alert for when a purge fails and stale content keeps being served globally.
- Which Cloudflare authentication model does this bundle assume?
- Bundles of this vintage commonly assume the legacy global API key plus account email pair. Modern Cloudflare uses scoped API tokens bound to specific zones and permissions, so verify which client generation the bundle pins before adopting it. This is a security-review gap rather than a cosmetic one.
- Can I use this bundle with multiple Cloudflare zones or a multi-tenant app?
- No. The zone ID comes from static bundle configuration and there is no tenant isolation, so a misconfigured value can purge the wrong tenant's cache. In a multi-tenant application, credentials and zone IDs must be derived from the tenant record rather than a config lookup.
- How is the Cloudflare bundle configured in a Symfony application?
- In Symfony you register the bundle in bundles.php and place credentials and zone settings under config/packages. That configuration tree is compiled by the bundle's DI extension, which is exactly the mechanism Laravel does not provide.
- How do I test Cloudflare cache purging without hitting the real API?
- The bundle ships no built-in fake or HTTP recording layer, so you would mock or swap the underlying Cloudflare client and assert the purge call shape. In Laravel, Http::fake is simpler and lets you assert the exact request without pulling in the bundle at all.
- What are the best alternatives to happyr/cloud-flare-bundle for Laravel?
- For Laravel, the official Cloudflare PHP SDK wrapped in a thin in-house service is the cleaner fit, and there are Laravel-specific Cloudflare packages as well. Also settle whether you only need URL purge or Enterprise Cache-Tag purge, since that drives call volume and queue design by an order of magnitude.
- Is happyr/cloud-flare-bundle actively maintained and safe for production?
- Maintenance signals are weak: a handful of stars, no dependents, no security triage, and no visible release cadence. Treat it as a reference implementation that reveals the right parameters and endpoints rather than a runtime dependency you rely on in production.
Weaver
How can I help you explore Laravel packages today?