Reply to thread

Message

Opcode memory cache is not shared by different SAPIs (like CLI, CGI, FPM, LSAPI, etc.) so there simply isn't a direct way to invalidate opcache from CLI.

Depending on the setup / environment there might not even be a process running the "web" SAPI on the same machine/ container running CLI.

One approach (that should work in many cases, but not necessarily every case) could be to use the XenForo API, eg. send an API request to the webserver from CLI.

[QUOTE="Kirby, post: 1589206, member: 1059"] Opcode memory cache is not shared by different SAPIs (like CLI, CGI, FPM, LSAPI, etc.) so there simply isn't a direct way to invalidate opcache from CLI. Depending on the setup / environment there might not even be a process running the "web" SAPI on the same machine/ container running CLI. One approach (that should work in many cases, but not necessarily every case) could be to use the XenForo API, eg. send an API request to the webserver from CLI. [/QUOTE]

Verification

Reply to thread

We value your privacy