Method for clearing object caches which are not available on the command line

[markjaquith]

I use my APC Object Cache plugin on a lot of single-server installs, and on my locally hosted dev versions thereof. But APC isn't available when PHP runs on the command line. So if I activate a plugin with WP-CLI, then check it through a web server, it won't be activated until I restart PHP or otherwise flush the APC cache.

I'd like to think up a way that this could be done from the command line, so I can run WP-CLI commands, flush out the cache, and then go on my way. As we don't have access to APC, it'll have to involve some sort of command-line-to-WordPress-running-on-a-web-server communication.

Ideas:

1. Trigger an HTTP request that the WordPress install will respond to.
2. Update a flag somewhere in the database, the checking of which on the web server version will somehow skip the cache, and then trigger the flush. Perhaps a direct query on an option.

Any other ideas?

[scribu]

What about the apc.enable-cli directive?

[markjaquith]

My understanding was that you don't get a persistent cache on the command line. Emphasis added:

Mostly for testing and debugging. Setting this enables APC for the CLI version of PHP. Under normal circumstances, it is not ideal to create, populate and destroy the APC cache on every CLI request, but for various test scenarios it is useful to be able to enable APC for the CLI version of PHP easily.

[joehoyle]

I have run into this issue (though with phpunit, but I think the same applies). When using APC via CLI, you don't get access to the same persistant cache. I ended up working around it by switching to memcache unfortunately.

Only other way I know how to clear the apc cache is to restart FPM / Apache or whatever server you may be using, which may be overkill.

[scribu]

Closing, since I'm not keen on the HTTP-based solution.

LE: Still, if someone ends up implementing it as a plugin or otherwise, do share.

[Rarst]

Hit this issue as linked above. I don't see easy solution so far.

Maybe for a start wp-cli shouldn't perform related commands in environment they are known to fail? wp cache type seems to detect "APC" as object cache, maybe it should be flag to lock out commands affected by the issue for now?

[scribu]

Yeah, throwing an error when APC is detected was what I had in mind.