Bugfix/redis cache backend #143
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
Kanti
reviewed
Jun 14, 2024
| 'database' => 0, | ||
| 'hostname' => 'redis', | ||
| 'port' => 6379, | ||
| ], |
There was a problem hiding this comment.
The example shows a possibility to keep this cache also the page cache is cleared. That might make sense in many cases
Kanti
approved these changes
Jun 17, 2024
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.
In reaction to #63 i checked the extension using redis. If redis cache lifetime is overdue, it might report it still "has" an object, but getting it returns "false".
Also to allow persistent caches which might be a valid solution if all file transfers are passed through TYPO3, i removed the clear-cache call on initialization.