Remove static cache support #820
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Use Joomlatools Server instead
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR Closes #819 and removes the static cache support. The implementation has been replaced by the cache middleware in Joomlatools Server which offers the same performance benefits without the need to store an additional cache and setup Apache rewrite rules.
Details
The middleware in Joomlatools Server uses Swoole and implements an active cache proxy that understand the Pages http cache and removes the need to store additional static files and setup additional and complex Apache rewrite rules.
The performance benefits remains the same. When running in Joomlatools Server, you now have 2 levels of caching:
The Joomlatools Server cache is a little simpler, then the Pages cache, if it cannot figure out if a request can be served from cache it will forward the request through FastCGI to Pages which will handle it, if Pages decides that the cache is no longer valid the page will be regenerated. Any cache revalidation requests are automatically forwarded to Pages.
Bonus: If you combine Joomlatools Server with a Fly.io’s multi-region deployment you effectively get your own active CDN.