Toshaan Bharvani
6 months ago
2 changed files with 24 additions and 0 deletions
@ -0,0 +1,13 @@ |
|||||||
|
; Enable ffi extension module |
||||||
|
extension=ffi |
||||||
|
|
||||||
|
; FFI API restriction. Possibe values: |
||||||
|
; "preload" - enabled in CLI scripts and preloaded files (default) |
||||||
|
; "false" - always disabled |
||||||
|
; "true" - always enabled |
||||||
|
;ffi.enable=preload |
||||||
|
|
||||||
|
; List of headers files to preload, wildcard patterns allowed. |
||||||
|
; /usr/share/php/preload used by for RPM packages |
||||||
|
; /usr/local/share/php/preload may be used for local files |
||||||
|
ffi.preload=/usr/share/php/preload/*.h:/usr/local/share/php/preload/*.h |
@ -0,0 +1,11 @@ |
|||||||
|
; 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. |
||||||
|
|
Loading…
Reference in new issue