Skip to content

Add update scripts information for zero downtime deployments #1966

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lauritsen wants to merge 2 commits into
base: 6.x
Choose a base branch
from
Open

Add update scripts information for zero downtime deployments #1966

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9923aab
Add zero downtime deployment info in configuring-update-scripts.md
lauritsen Aug 18, 2026
66e7c0d
Add update scripts info in zero-downtime-deployments.md
lauritsen Aug 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions content/collections/tips/configuring-update-scripts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,3 +36,12 @@ php please updates:run 3.0
:::tip
This is a one-time thing and will be automatically triggered by future Statamic updates.
:::

### Running update scripts when doing zero downtime deployments

Since zero downtime deployments typically use a multiple-release directory structure, where each new deployment is a fresh installation of the application, update scripts can be missed.
To ensure update scripts are run, add a step to your deployment pipeline that makes a backup of the `composer.lock` file.
``` shell
# Backup composer lock file to ensure update scripts are run
cp composer.lock storage/statamic/updater/composer.lock.bak
```
9 changes: 9 additions & 0 deletions content/collections/tips/zero-downtime-deployments.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,15 @@ Every deployment has its own timestamped release directory, with a fresh clone o

After a successful deployment, the `current` folder is then symlinked to the latest release. This symlink swap is the secret sauce for zero downtime.

### Ensure update scripts are run

Since each new deployment is a fresh installation of the application, update scripts can be missed.
To ensure update scripts are run, add a step to your deployment pipeline that makes a backup of the `composer.lock` file.
``` shell
# Backup composer lock file to ensure update scripts are run
cp composer.lock storage/statamic/updater/composer.lock.bak
```

## Cache storage

Statamic's content management heavily relies on caching, and sometimes it's necessary for the [Stache](/stache) to store absolute file paths in your app's cache. This can lead to deployment errors when users are hitting your frontend, since each release [exists in a separate timestamped folder](#understanding-the-folder-structure).
Expand Down