|
| @@ -8 +9,3 @@ |
| /opt/php84/extensions/ ← the .so files
|
| /opt/php84/extensions/ -> the .so files |
|
In order to run 'php84' we can select the correct ini files. The base php.ini and the extensions ini files both need overriding. |
|
|
| @@ -13,2 +15,0 @@ |
|
|
In order to run 'php84' we can select the correct ini files. The base php.ini and the extensions ini files both need overriding.
|
|
|
| @@ -17 +18,2 @@ |
| and then the copy can be tested using.
|
| and then the copy can be tested using. But first we need to create the tmp file that the php8.4 copy will use. |
|
|
|
|
| @@ -26,5 +29,10 @@ |
sed -i 's|php-fpm.sock|php84-fpm.sock|g' /etc/webstack/nginx/vhosts.d/*.conf
|
Then on both servers nginx can be checked and restarted
|
| nginx -t
|
| systemctl restart nginx
|
| Checking that on srv9 first and confirming https://rdm1.uk:8443/phpinfo.php shows php using the right ini sources before repeating on srv10.
|
|
|
| sed -i 's|php-fpm.sock|php84-fpm.sock|g' /etc/webstack/nginx/vhosts.d/*.conf |
|
Then on both servers nginx can be checked and restarted
|
| nginx -t systemctl restart nginx Checking that on srv9 first and confirming https://rdm1.uk:8443/phpinfo.php shows php using the right ini sources before repeating on srv10. |
While a little 'after the horse has bolted', preventing SUSE from over writing the PHP8.4 release of PHP should have been blocked. The SUSE does not properly handle this as it did between php7 and php8 is somewhat irritating and certainly being able to actually select between php84 and php85 is the object here. While sorting out the mess on srv10 I locked things on desktop and srv9, and removed the lock once I was happy that php84 was protected. |
|
| zypper addlock "php8*" |
| zypper removelock "php8*" |
|
|
