cd /usr/local/directadmin/custombuild
mkdir -p custom/opcache
cp -p configure/opcache/opcache.ini custom/opcache/opcache.ini
Code:
nano custom/opcache/opcache.ini
Code:
./build opcache
Most values are still default and if DA changes something then it's mostly to benefit DA installations and normally you don't need a custom file for opcache.Well my question would be why did DA decide to alter the default opcache values?
opcache.restrict_api=1 <-- this one was for security reasons.
Correct.Unless you get the error:
/usr/local/php83/bin/php -d memory_limit=512M -d opcache.restrict_api=""
So in theory that does nothing and users can call the api even if it's disabled in opcache.ini?
Yes that’s my experience. New default OPCache settings, nextcloud was complaining about restricted API access. Warning went away with the directive in the cron job in my previous post, with no changes to server configCan the restriction be disabled when PHP is used as PHP-FPM for a website?