-
Notifications
You must be signed in to change notification settings - Fork 74
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
Migrate caching to Surge? #771
Comments
What's the intention behind it? Something simpler and with less options? I'm unaware of any of the existing shortcomings or issues that the current plugin has though, so I tend to err on the side of don't touch it if it's working. WordPress.org pretty much exclusively uses nginx caching, which doesn't have purge support, but is only for logged out users and short cache ttl's. |
Thanks for considering this! I'll be happy to help with the setup (there isn't much, really), and any custom configuration you might need, like invalidating things on certain custom events. |
Yeah, I think that's a good instinct in general.
The aren't any tangible problems at the moment, but in the past we've run into a few:
The simplicity of Surge is appealing as a way to minimize the chances of that stuff in the future, and to remove some of the customizations we've added with something that "just works". It'd also give us caching for There's always the chance that it could introduce new problems, though. The lack of preloading would probably be a performance hit, too. We could mitigate it to some extent w/ a longer TTL. I think it'd be nice, but don't feel strongly. |
That alone would make it worth investigating IMHO. Especially given some current (and many future) things are likely built on top of it. |
I always like simplifying things, so 👍 from me. Maybe we could roll Surge out in phases, starting tests with a small number of old WordCamp sites and gradually testing more with upcoming events before sunsetting WP Super Cache completely? Let me know if there's anything I can help with these efforts :) |
If we do this we should also grep the code for |
Our own @kovshenin released a lean caching plugin that looks really good. It'd be simpler and cleaner than WPSC, so I think we should consider migrating.
We could use nginx microcache if want to go even further, but that may not be worth it.
Any thoughts @ryelle @dd32 @coreymckrill?
The text was updated successfully, but these errors were encountered: