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.
Hello there,
This PR is a proposal. It addresses the PHP OPcache reset after a new release is published.
The idea was inspired by the TYPO3/Surf deployment project. It features two tasks which create and execute a simple PHP script to reset the OPcache. As the OPcache memory space of the web server differs from that of the CLI interpreter, the script must be executed by the web server. To achieve this, the PHP script is placed in the document root of the release and fetched from the web server after the release is published.
For Deployer, the mechanics were adapted into an recipe which consists of two grouped task
These tasks have not yet been included in any deployment recipe because they are still in the experimental stage.
There are several considerations to take into account:
reset_opcache_document_rootto their specific path.reset_opcache_app_url. This configuration option likely needs improvement.fetch()function does not offer any options for handling untrusted HTTPS connections in development environments. Direct use ofHttpiewould be an alternative approach to solve this issue.Please let me know what you think.