Hi @tyke79,
For example, my server is centos and the opcache configuration is placed in /etc/php.d/10-opcache.ini
From opcache.ini file, it has opcache.blacklist_filename directive and this is how it looks like;
; The location of the OPcache blacklist file (wildcards allowed).
; Each OPcache blacklist file is a text file that holds the names of files
; that should not be accelerated.
opcache.blacklist_filename=/etc/php.d/opcache*.blacklist
You can define where the path you want to opcache exclude it from a cache in file /etc/php.d/opcache*.blacklist that resolves to /etc/php.d/opcache-default.blacklist, this is how it looks like:
; The blacklist file is a text file that holds the names of files
; that should not be accelerated. The file format is to add each filename
; to a new line. The filename may be a full path or just a file prefix
; (i.e., /var/www/x blacklists all the files and directories in /var/www
; that start with 'x'). Line starting with a ; are ignored (comments).
; Files are usually triggered by one of the following three reasons:
; 1) Directories that contain auto generated code, like Smarty or ZFW cache.
; 2) Code that does not work well when accelerated, due to some delayed
; compile time evaluation.
; 3) Code that triggers an OPcache bug.
;/home/awiedev/wpdev/wpdev-web/woodev
Thanks.