Repository navigation
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.shhas a newreloadaction (a graceful reload that doesn't drop in-flight requests), and it now rejects PHP versions that aren't in the8.4form.
Upgrading
curl -sSL https://raw.githubusercontent.com/crivion/laranode/refs/heads/main/laranode-scripts/bin/laranode-upgrade.sh | bashOnce it finishes, check that the commit the upgrader prints matches this release.