Level 54
Are you sure it's not a client-side browser cache issue?
Jun 28, 2016
8
Level 5
Laravel elixir file_get_contents cache?
When Elixir does file_get_contents to parse the rev-manifest.json file, does that data get cached somewhere? We are having issues with our deployments. When we deploy we sort of do what Envoyer does whereby we create a new release in a releases folder, do the deployment of the code, and then when its complete we re-point our nginx set folder to the new timestamped release folder.
The strange thing is that for a while after this process, somehow our files are still looking for the old revisioned js and css files from the previous rev-manifest.json file, even though the current web folder is the new release folder. So the data from rev-manifest.json is being cached somewhere.
We have tried clearing all know caches which to my under standing are /storage/framework/cache and /storage/framework/views. We also run php artisan cache:clear, php artisan view:clear, php artisan optimize, composer dump-autoload. Yet for up to an hour the site still tries to use the old css and js files which do not exist in the newly made release folder and thus throw a 404.
Interested to see if anyone has any thoughts. Are there other caches I don't know about?
Level 5
@willvincent yeah tried it with a fresh browser as well. Same issue.
Level 54
Any load balancers or http cache server (varnish, etc) in your webstack?
Level 5
Nope. Though we are looking further into that. Our server people say its a Laravel thing. Honestly I am not sure at this point.
Level 54
Shooting blind here, but this might help: http://stackoverflow.com/questions/29844232/running-gulp-tasks-with-laravel-elixir-doesnt-version-all-js-files
Level 65
So you confirmed these two things?
- Confirmed the new rev-manifest.json is correct when doing
cat public/build/rev-manifest.json. - Confirmed the files in /public/build have updated to link up to the rev-manifest.json file.
I've never seen that issue where it's been cached. I've pulled new code and it's worked straight away.
The only thing I know which is cached PHP side is symlinks. This means that real paths (release folder) are cached by the system and will return the old one until it's updated. Have a check by modifying the old rev-manifest.json when looking at the source for it on your domain (domain.tld/build/rev-manifest.json).
Level 5
I think symlinks is the issue. I am going to go deep down that path and let you know what I find out.
Level 5
Ok everyone. Found the answer. So yeah the issue is that on php versions greater than 5.5, symlinks cache in a very unpredictable way. So the short answer is to restart php-fpm at the end of the process. Envoyer does this as well.
Here is a nice post on it.
http://codinghobo.com/opcache-and-symlink-based-deployments/
Please or to participate in this conversation.