PHP8.0 would stop receiving security support on 26 Nov 2023
hence this deprecation. Next, is the eventual drop of PHP8.0 before its EOL.
This commit also updates the message type from INFO to WARNING if the php
on file has reached its EOL.
See: https://www.php.net/supported-versions.php
Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
JPEG previews are not correctly oriented when exif is not enabled
along with other issues. There's no easy way to discover this either.
Signed-off-by: Varun Patil <varunpatil@ucla.edu>
which disables shared memory based OPcache with disk file cache used only, if enabled. In this case, "opcache.memory_consumption" and others do not apply, so show the correct performance recommendation to enable memory cache.
Signed-off-by: MichaIng <micha@dietpi.com>
With #32902 it was meant to be avoided to recommend raising the interned strings buffer size above a quarter of the total OPcache size. This works as long as there is at least 1 byte free, but does not apply if the buffer is filled completely.
This commit switches the conditions so that the interned strings buffer size must be smaller than a quarter of the total OPcache size for the warning to be shown. That the buffer must be either filled completely or by more than 90% remains untouched.
Signed-off-by: MichaIng <micha@dietpi.com>
The two tables seem to have gone out of sync, causing the web interface
to miss `files_trash.auto_id` not being a bigint.
Signed-off-by: Michael Kuhn <github@ikkoku.de>
A link to the Nextcloud documentation is currently only shown when the OPcache module is not loaded at all. This commit moves the link to the generic text above the individual recommendations list.
Additionally remove the obsolete phpOpcacheDocumentation entry from test data arrays, which is not passed anymore by the backend.
Signed-off-by: MichaIng <micha@dietpi.com>
The current OPcache recommendations match the PHP defaults, but the values are much higher than required to run Nextcloud, even with a high number of installed apps. On the other hand, when other applications use the same OPcache instance, the recommended values might not be sufficient. Accurate recommendations need to take into account actual OPcache usage.
With this commit, recommendations are shown to raise the config value if more than 90% of max cache size or number of keys is used.
The checks whether the module is loaded and whether the OPcache is properly configured have been merged into a single function. This allowed to reduce the overhead of OPcache configuration checks when the module is not loaded.
A check has been added whether Nextcloud is permitted to use the OPcache API. Without this, inconsistencies during core or app upgrades may cause errors and OPcache usage cannot be determined for the new usage based checks.
OPcache usage based checks are skipped when Nextcloud is not permitted to use the API.
Signed-off-by: MichaIng <micha@dietpi.com>