Download the PHP package silber/page-cache without Composer

Laravel Page Cache

This package allows you to easily cache responses as static files on disk for lightning fast page loads.

• Introduction
• Installation
  • Service Provider
  • Middleware
  • URL rewriting
  • Ignoring the cached files
• Usage
  • Using the middleware
  • Clearing the cache
  • Customizing what to cache
• License

Introduction

While static site builders such as Jekyll and Jigsaw are extremely popular these days, dynamic PHP sites still offer a lot of value even for a site that is mostly static. A proper PHP site allows you to easily add dynamic functionality wherever needed, and also means that there's no build step involved in pushing updates to the site.

That said, for truly static pages on a site, there really is no reason to have to boot up a full PHP app just to serve a static page. Serving a simple HTML page from disk is infinitely faster and less taxing on the server.

The solution? Full page caching.

Using the middleware included in this package, you can selectively cache the response to disk for any given request. Subsequent calls to the same page will be served directly as a static HTML page!

Installation

Note: The current version of Page Cache requires PHP 8.2+ and Laravel 11+.

If you're on Laravel v5-v10, use Page Cache v1.0.9.

Install the page-cache package with composer:

Middleware

Open app/Http/Kernel.php and add a new item to the web middleware group:

The middleware is smart enough to only cache responses with a 200 HTTP status code, and only for GET requests.

If you want to selectively cache only specific requests to your site, you should instead add a new mapping to the middlewareAliases array:

Once registered, you can then use this middleware on individual routes.

URL rewriting

In order to serve the static files directly once they've been cached, you need to properly configure your web server to check for those static files.

• For nginx:

  Update your location block's try_files directive to include a check in the page-cache directory:

• For apache:

  Open public/.htaccess and add the following before the block labeled Handle Front Controller:

Ignoring the cached files

To make sure you don't commit your locally-cached files to your git repository, add this line to your .gitignore file:

Usage

Using the middleware

Note: If you've added the middleware to the global web group, then all successful GET requests will automatically be cached. No need to put the middleware again directly on the route.

If you instead registered it in middlewareAliases, you should use the middleware on whichever routes you want to be cached.

To cache the response of a given request, use the page-cache middleware:

Every post will now be cached to a file under the public/page-cache directory, closely matching the URL structure of the request. All subsequent requests for this post will be served directly from disk, never even hitting your app!

Clearing the cache

Since the responses are cached to disk as static files, any updates to those pages in your app will not be reflected on your site. To update pages on your site, you should clear the cache with the following command:

As a rule of thumb, it's good practice to add this to your deployment script. That way, whenever you push an update to your site, the page cache will automatically be cleared.

If you're using Forge's Quick Deploy feature, you should add this line to the end of your Deploy Script. This'll ensure that the cache is cleared whenever you push an update to your site.

You may optionally pass a URL slug to the command, to only delete the cache for a specific page:

To clear everything under a given path, use the --recursive flag:

For example, imagine you have a category resource under /categories, with the following cached pages:

• /categories/1
• /categories/2
• /categories/5

To clear the cache for all categories, use --recursive with the categories path:

Customizing what to cache

By default, all GET requests with a 200 HTTP response code are cached. If you want to change that, create your own middleware that extends the package's base middleware, and override the shouldCache method with your own logic.

1. Run the make:middleware Artisan command to create your middleware file:

2. Replace the contents of the file at app/Http/Middleware/CacheResponse.php with this:

3. Finally, update the middleware references in your app/Http/Kernel.php file, to point to your own middleware.

License

The Page Cache package is open-sourced software licensed under the MIT license.