Skip to content

v1.2.5 — Restores now clear OPcache for the site's PHP version

Latest

Choose a tag to compare

@crivion crivion released this 23 Sep 14:19
· 4 commits to main since this release
8a0a4b2

Fixed

  • A restored website could keep serving its old code. Restored files keep their original paths, so on servers with opcache.validate_timestamps=0, PHP-FPM kept running the code it had cached before the restore. The restore now reloads PHP-FPM once for each PHP version that serves a restored site. The version is taken from the site's current settings, not from the backup, so a site switched to another PHP version since the backup gets the right one reloaded. If a reload fails, the restore is marked failed with a message saying the files were restored and PHP-FPM needs a reload.

Changed

  • laranode-php-service.sh has a new reload action (a graceful reload that doesn't drop in-flight requests), and it now rejects PHP versions that aren't in the 8.4 form.

Upgrading

curl -sSL https://raw.githubusercontent.com/crivion/laranode/refs/heads/main/laranode-scripts/bin/laranode-upgrade.sh | bash

Once it finishes, check that the commit the upgrader prints matches this release.