fix: no longer automatically execute cachetool task #104
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.
Issue
Currently the Hypernode deploy always executes the cachetool opcache flush task.
This task is extremely flakey and fails a lot on our end. Same issue as on the Hipex servers.
Solution
This task can be safely removed, or at least marked optional as it's not required on Hypernode.
For reference see: https://deployer.org/docs/7.x/avoid-php-fpm-reloading
And in the Hypernode NGINX configuration
/etc/nginx/fastcgi_params
the following linefastcgi_param SCRIPT_FILENAME $realpath_root$fastcgi_script_name;
Which makes it so that no longer opcache has to be flushed.
I've tested this and validated this on multiple customers on our end.