Download the PHP package artformdev/craft-edge without Composer
On this page you can find all versions of the php package artformdev/craft-edge. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download artformdev/craft-edge
More information about artformdev/craft-edge
Files in artformdev/craft-edge
Package craft-edge
Short Description Full-page HTML edge caching for Craft CMS at one edge tier (nginx or Cloudflare), with exact element-driven invalidation and CSRF/session-safe hydration.
License proprietary
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package craft-edge
Edge
Full-page HTML caching for Craft CMS 5, without the usual footguns.
Edge serves your anonymous visitors their pages straight from the edge (a folder of static files, nginx's FastCGI cache, or Cloudflare) with PHP and the database never running. The hard parts of full-page caching (not leaking one person's session to the next, and never serving stale content after an edit) are the parts Edge is actually built around.
- Hits skip PHP entirely. An anonymous page view is answered by nginx or Cloudflare in single-digit milliseconds. Craft doesn't boot.
- Session leaks are structurally impossible. Cacheable responses are stored stripped of every cookie; there is no code path that caches a response carrying someone's session.
- Invalidation is exact. When an editor saves, Edge purges every URL that rendered the changed element or ran a query the change affects: detail pages, listings (including brand-new entries), related pages, nav, in background jobs, within seconds.
- Cached pages stay personal. Forms, CSRF tokens, carts and greetings keep working via tiny uncached "islands" hydrated in the browser. No framework, no build step.
How it works, in one picture
A cached page is an anonymous shell, identical for everyone, stored cookie-free and served from the edge, with a few personal holes filled in the browser from endpoints that are never cached:
Anonymous cookies (CraftSessionId, CSRF) are ignored so returning visitors still get
hits, and login cookies are ignored too: signed-in visitors get the same shared shell as
everyone else, with their account menu, cart and CSRF tokens hydrated client-side from
uncached endpoints. It's a small set of ideas that fit together. The
How Edge works guide walks through all of them, and it's worth
ten minutes before you turn caching on.
Install
Then pick a driver and prepare its edge tier. Installing the plugin doesn't cache anything on its own; something in front of PHP has to store and serve the copies:
| Where you host | Driver | Guide |
|---|---|---|
| Single server / VPS (simplest, start here) | nginx-static |
nginx-static |
| You use nginx's FastCGI cache | nginx-fastcgi |
nginx-fastcgi |
| Behind Cloudflare | cloudflare |
Cloudflare |
Copy the config file and confirm your first hit:
Then schedule the refresh task, so scheduled posts and expiring entries reach the cache — Craft fires no event when a date passes, so nothing else notices:
Full walkthrough: Installation.
Documentation
The complete guide lives in docs/. Read it in order the first time:
- How Edge works: the mental model. Start here.
- Installation: install, pick a driver, first hit.
- Drivers: nginx-static, Cloudflare. Each covers preparing the environment, connecting Edge, and verifying.
- Configuration reference: every setting, in depth.
- Templating for the cache: the anonymous shell, forms & CSRF, islands, and the patterns that quietly break caching. The key page for developers.
- Invalidation & warming: how a save becomes the right purges.
- CLI & control panel: commands and the utility.
- Troubleshooting: reading the headers, and fixing the usual suspects.
At a glance
Requirements: Craft CMS 5.0+, PHP 8.2+, a running queue, and one edge tier
(any nginx for nginx-static; nginx + ngx_cache_purge for nginx-fastcgi; or a Cloudflare
zone).
The cookie model (the thing that makes it safe):
| Cookie class | Examples | What Edge does |
|---|---|---|
| Anonymous | CraftSessionId, CSRF token, PHPSESSID, Craft's login cookies |
Ignored: never key, bypass, or vary. Signed-in visitors share the anonymous shell and personalize client-side. |
| Opt-in bypass | your bypassCookies (empty by default), e.g. a live cart cookie |
Bypass: always dynamic. |
Set-Cookie on a cacheable response |
any | Stripped before storing: if one survives, the page isn't stored at all. |
Never stored, ever: non-GET requests; CP / action / preview / token requests; logged-in
renders (a signed-in visitor is served the shared anonymous copy, but their own render is
never persisted); requests with a bypass cookie; non-200 or redirect responses; anything
still carrying a Set-Cookie. A cache-write failure (read-only disk, etc.) never breaks the
page: it's logged and served dynamically.
Common commands:
License
Commercial plugin, see LICENSE.md (Craft license).
