-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[INQUIRY] - Status of this project as of 2019? #158
Comments
Hi @7php, Thanks for the issue.
It's available for use with one significant known issue #138
No, LCache isn't in wide deployment. WP Redis is the recommended persistent object cache: https://github.com/pantheon-systems/wp-redis
Do you have any recommendations on how this could be communicated?
I'm not sure where it mentions Varnish with WP-LCache on that document. Here's the most up-to-date resource on Pantheon's full-page cache https://pantheon.io/global-cdn |
Hi @danielbachhuber
I think an updated message on the plugin repo itself - on the readme of the github repo + on the WP plugin page, where you can advise users that due to that issue, the recommended approach is to use the WP Redis. I appreciate and love all that you and the Pantheon are doing. Simply brilliant. cheers |
Thanks for the suggestion, @7php @davidstrauss Are you amenable to this? |
@danielbachhuber I think that's a good recommendation at this juncture. |
cheers @danielbachhuber |
Hey there @danielbachhuber , @joshkoenig and Pantheon team.
Asking, because some issues here dating 2017 has not been resolved yet and the last real code change "commit" probably was 2yrs ago.
This plugin, as I once mentioned, seemed very promising. But if it is no more active and not making sense, kindly communicate it upfront to prevent people investing time on deploying this. ;) But I am hoping all is well.
Also, an additional question if I may ask:
3) On Pantheon's server infrastructure, you don't use Redis or Nginx revers proxy caching?
I read here that it uses Varnish with Wp-Lcache - want to confirm if this is still the same?
Cheers.
The text was updated successfully, but these errors were encountered: