Weave Code
Statamic Cloudflare Purge Laravel Package
justbetter/statamic-cloudflare-purge
A Statamic addon that automatically purges your Cloudflare cache whenever content changes, so visitors always see fresh pages after edits, new entries, or updates. Simple to install and configure.
At a glance
Frequently asked questions about Statamic Cloudflare Purge
- What does justbetter/statamic-cloudflare-purge do?
- It is a Statamic addon for Laravel applications that automatically purges your Cloudflare cache whenever content changes. After edits, new entries, or updates, the addon helps ensure visitors see fresh pages instead of stale cached versions. It is designed to be simple to install and configure within a Statamic project.
- How do I install justbetter/statamic-cloudflare-purge?
- Install it with Composer as a dependency in your Statamic and Laravel project, then follow the addon's installation steps. You will typically publish any configuration and add your Cloudflare credentials before enabling automatic purging. Check the repository README for the exact Composer command and any required Statamic addon registration steps.
- Which Laravel and Statamic versions are supported?
- The package is a Statamic addon built for Laravel applications, so your Laravel version must match what your Statamic release supports. Exact version constraints are defined in the package's composer.json and README. Check those constraints before installing, especially if you are on an older Laravel or Statamic version.
- How do I configure Cloudflare API credentials for this addon?
- You need to provide Cloudflare API credentials so the addon can request cache purges for your zone. In practice that means creating a scoped Cloudflare API token and supplying it, along with your Cloudflare zone ID, through the addon's configuration. Use the published config file and README as the source of truth for exact option names.
- When does the addon purge the Cloudflare cache?
- It purges the Cloudflare cache when Statamic content changes, such as edits, new entries, and updates. The goal is to keep front-end pages fresh after content management actions. Review the addon configuration if you need to understand which content events trigger purges in your setup.
- Can I purge specific URLs instead of the whole Cloudflare cache?
- The addon's core purpose is automatic purging when content changes, so the available targeting options depend on its configuration and implementation. Check the published config and README for supported purge modes before assuming URL-level or tag-level purging. For advanced selective purging you may also need to extend the addon or call the Cloudflare API directly.
- Will this package slow down saving content in Statamic?
- The addon makes Cloudflare API requests when purges are triggered, so response time can depend on Cloudflare and how the addon dispatches those requests. Test content saves in staging and monitor production behavior if you publish frequently. If save latency matters, review whether the addon supports queueing or other async options in its configuration.
- How can I test that Cloudflare cache purging works?
- Make a content change in Statamic, then check that the affected page returns fresh content rather than a cached Cloudflare response. Use Cloudflare analytics or purge history, and compare responses with cache headers or a cache-busting query string. Test in a staging environment with a scoped token before enabling it on production.
- Is it safe to use in production with a Cloudflare API token?
- Yes, provided you use a narrowly scoped Cloudflare API token that can only purge cache for the intended zone. Store credentials in environment variables or your Laravel configuration rather than committing them. Test the integration in staging first and rotate the token if it is ever exposed.
- What are alternatives to justbetter/statamic-cloudflare-purge?
- Alternatives include manually purging the Cloudflare cache, writing custom Statamic event listeners that call the Cloudflare API, or using other cache-purge addons. This package is a focused option when you want automatic purging on content changes without building the integration yourself. Compare maintenance status and configuration needs against your project's requirements.
Weaver
How can I help you explore Laravel packages today?