OK -- so the word from WPE is that it is not possible to do this programmatically via an API or some such thing, at least for now.
If we were able to use git deployment rather than sftp, this would be handled automatically. However, as we've established, git deployment with WPE does not work properly for us.
So, the other option we have is to build some headless "browser" that logs in and clicks the purge cache button after deploy.
We do have a framework for doing these kinds of things via the wp.cmd task, but it would still require some reverse engineering and may be more trouble than it's worth.
OK -- so the word from WPE is that it is not possible to do this programmatically via an API or some such thing, at least for now.
If we were able to use git deployment rather than sftp, this would be handled automatically. However, as we've established, git deployment with WPE does not work properly for us.
So, the other option we have is to build some headless "browser" that logs in and clicks the purge cache button after deploy.
We do have a framework for doing these kinds of things via the
wp.cmd
task, but it would still require some reverse engineering and may be more trouble than it's worth.