Opt-out of static cache clearing on deploy #117

timkelty · 2025-11-07T15:08:51Z

timkelty
Nov 7, 2025
Maintainer

By default, Craft Cloud runs craft cloud/up following deploys, which:

Runs craft up (migrations + project-config)
Full static cache purge

Originally, static caches always needed to be purged, as cdn.craft.cloud artifact URLs contain a build ID that changes on each deployment.

With rewrites, you can avoid that entirely, so we should make cache clearing optional.

Additionally, by using ESIs, you may want to purge more selectively (e.g. just your layout's html <head> contents), so you don't need to fully invalidate.

You can control the behavior of cloud/up via events, but we plan on making this easier and more customizable in future releases:

        // Prevent static cache clear on deploy
        Event::on(
            UpController::class,
            UpController::EVENT_BEFORE_UP,
            function (CancelableEvent $event) {
                $event->sender->run('/setup/php-session-table');
                $event->sender->run('/setup/db-cache-table');

                if (Craft::$app->getIsInstalled()) {
                    $event->sender->run('/up');
                }

                Craft::$app->end();
            }
        );

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Opt-out of static cache clearing on deploy #117

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 0 comments

Select a reply

Uh oh!

Opt-out of static cache clearing on deploy #117

Uh oh!

Uh oh!

timkelty Nov 7, 2025 Maintainer

Replies: 0 comments

timkelty
Nov 7, 2025
Maintainer