Multiple sockets for opcache #3363
Closed
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
This is needed if different instances run for multiple domains on one server
This was referenced Oct 31, 2022
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 extends the cachetool configuration, so that multiple sockets (e.g. for multiple domains) can be addressed. See updated documentation for details. A retry mechanism has been added because clearing the opcache for multiple sockets too fast can result in errors.
Also downloading the cachetool has been changed analogous to composer, to the
.depdirectoryFor backwards compatibility:
cachetoolconfiguration still works and has precedence, albeit undocumentedcachetool.pharis in the current/release path,it will be used