laravel php artisan cache clear
Laravel 5 Clear Views Cache
I notice that Laravel cache views are stored in
/storage/framework/views. Over time, they get to eat up my space. How do I delete them? Is there any command that could? I tried php artisan cache:clear, but it is not clearing the views cache. With that, I have to manually delete the files in the said folder.
Also, how do I disable the views caching?
8 Answers 8
There is now a php artisan view:clear command for this task since Laravel 5.1
To get all the artisan command, type.
If you want to clear view cache, just use:
If you don’t know how to use specific artisan command, just add «help» (see below)
please try this below command :
To answer your additional question how disable views caching:
You can do this by automatically delete the files in the folder for each request with the command php artisan view:clear mentioned by DilipGurung. Here is an example Middleware class from https://stackoverflow.com/a/38598434/2311074
However you may note that Larevel will recompile the files in the /app/storage/views folder whenever the time on the views files is earlier than the time on the PHP blade files for the layout. THus, I cannot really think of a scenario where this would be necessary to do.
Laravel Clear Cache Using Artisan Command
Table of Content
If you are making a lot of changes to your views and configurations then you might have encountered the problem I can’t see my changes, you should run the Laravel clear cache command in your terminal.
When your application is in production mode you should try to leverage the cache as much as you can, but if your application is in the development mode then you can face some issues regarding the actual results you are looking for. This is due to some part of your application is served by the cache.
In this post, we will look at how we can use Laravel clear cache commands which you run in your terminal and what are the benefits of them.
Laravel Artisan
Laravel Artisan is a command line interface (CLI) which allows you to manage your application by running few commands. This interface also helps you to clear the cache of your application using the terminal.
Laravel Artisan also provides various commands which help you to generate various components of the Laravel’s framework. If you are developing the Laravel application for some time, you might already know the commands offered by Laravel Artisan’s CLI.
You can view all commands offered by Laravel Artisan using the below command:
Laravel Config Cache
Any Laravel application is based on the many configuration files which come with the Laravel’s installation and reside in config/ folder. Imagine, if you are using a modular approach in your application (As I do) then you will have to define a config file for each module. As soon as your application grows, your application will be heavily relying on Laravel’s configurations which will at some point slow down your application.
Laravel framework provides an easy mechanism to combine all those configuration files into one file using the below artisan command:
As soon as you will run the above command, you will see a significant improvement in your application’s performance.
Clearning Laravel’s Configuration Cache
If you study the Laravel’s framework, you will find out that at some places Laravel heavily use the configuration files to get certain values like database credentials. Let’s assume your application was running on the current server with the current configuration values.
For performance reasons, you have to move your application to a different server, in that case, you have to update all the configuration values.
What about the configuration values stored in the cache?
In this case, you have to clear the cache so that Laravel uses the current values for the configuration. Laravel provides a simple artisan command to clear all cached values. To clear cached values use the below command in the terminal.
Clearning Laravel’s Application Cache
Sometimes simply clearing application configuration files is not the solution. There is always a possibility that inconsistency can exist in your code base or application itself, this is where you have to clear the whole application’s cache.
In such a situation, all you have to do is clear cache on the application level using below artisan command:
Other Laravel Cache Clear Commands
Let’s list down all important commands which you can use to clear cache for a specific section.
Laravel Cache Clear
To clear the application’s cache on application level run the below command:
Laravel Clear Route Cache
To clear all the cached routes of your application run the below command:
Laravel Clear View Cache
If you have made any changes to your views and can’t see the changes or any views related error which you are one hundred percent sure it’s fixed, then it might be an indication that you have to clear the cached views.
Run below command in the terminal to clear all cached views:
Conclusion
In this short post, we looked at how we can clear the cache of the Laravel application, which not only will fix any errors you are facing also will boost the performance of your application. To learn more about how you can improve the Laravel’s application performance check our post on Laravel Performance Tips.
If you have any question or suggestions, please leave them in the comments box below.
Laravel Artisan Cache Commands Explained
Often times, when you are in the middle of developing a Laravel application, you may find that the changes you made in your code are not reflecting well on the application when testing.
Usually, the case is most likely caused by caching applied by the Laravel framework.
Here are some of the common commands you can run in your terminal to alleviate the issue.
❗️ Make sure you are running them in the context of your application. Meaning, your terminal is currently in the same directory as your Laravel application.
1. Configuration Cache
Caching configuration helps with combining all of the configuration options for your application into a single file which will be loaded quickly by the framework.
Clearing Configuration Cache
Exit fullscreen mode
If you want to quickly reset your configuration cache after clearing them, you may instead run the following command:
Exit fullscreen mode
Caching your configuration will also help clear the current configuration cache. So it helps save your time without having to run both commands.
2. Route Caching
Caching your routes will drastically decrease the amount of time it takes to register all of your application’s routes. When you add a new route, you will have to clear your route cache for the new route to take effect.
Clearing Route Cache
The following command will clear all route cache in your application:
Exit fullscreen mode
To cache your routes again, simply run the following command:
Exit fullscreen mode
Again, running the above command alone is enough to clear your previous route cache and rebuild a new one.
3. Views Caching
Views are cached into compiled views to increase performance when a request is made. By default, Laravel will determine if the uncompiled view has been modified more recently than the compiled view, before deciding if it should recompile the view.
Clearing View Cache
However, if for some reason your views are not reflecting recent changes, you may run the following command to clear all compiled views cache:
Exit fullscreen mode
In addition, Laravel also provides an Artisan command to precompile all of the views utilized by your application. Similarly, the command also clears the view cache before recompiling a new set of views:
Exit fullscreen mode
4. Events Cache
If you are using Events in your Laravel application, it is recommended to cache your Events, as you likely do not want the framework to scan all of your listeners on every request.
Clearing Events Cache
When you want to clear your cached Events, you may run the following Artisan command:
Exit fullscreen mode
Likewise, caching your Events also clear any existing cache in the framework before a new cache is rebuilt:
Exit fullscreen mode
5. Application Cache
Using Laravel’s Cache is a great way to speed up frequently accessed data in your application. While developing your application involving cache, it is important to know how to flush all cache correctly to test if your cache is working properly.
Clearing Application Cache
To clear your application cache, you may run the following Artisan command:
Exit fullscreen mode
❗️ This command will NOT clear any config, route, or view cache, which are stored in /bootstrap/cache/ directory.
6. Clearing All Cache
Laravel provides a handy Artisan command that helps clear ALL the above caches that we have covered above. It is a convenient way to reset all cache in your application, without having to run multiple commands introduced before.
To clear all Laravel’s cache, just run the following command:
Exit fullscreen mode
As you can read from the terminal feedback, all cache types that existed in your Laravel application will be cleared entirely, except Events cache.
🎁 Bonus
If the above Laravel’s Artisan commands don’t seem to resolve the issue you are facing, you may need to look at other related environments in your project that may be causing it.
When building a Laravel project, it is common to employ the Composer Dependency Manager for PHP, as well as NPM for any JavaScript library that might be needed in your project. We just have to take note that both package managers are using some form of caching for performance improvements.
Clearing Composer Cache
Sometimes, a new package you just installed via Composer doesn’t appear to be working at all. Or a new project you just cloned from a repository doesn’t seem to be running correctly.
Such issues are usually caused by classmap error from a newly installed library class, or the cached version of a particular library does not match with the ones required by the project codebase you just cloned. In such a situation, you need to update the PHP autoloader by running the following command:
Exit fullscreen mode
As well as any of the following variations(they all achieve the same purpose of deleting all content from Composer’s cache directories):
Laravel 5 – Clear Cache in Shared Hosting Server
The question is pretty clear.
Is there any workaround to clear the cache like the above command but without using CLI. I am using a popular shared hosting service, but as per my plan, I don’t have control panel access.
I want to clear the views cache.
I saw a question almost the same like this, but it doesn’t help me.
20 Answers 20
You can call an Artisan command outside the CLI.
Update
There is no way to delete the view cache. Neither php artisan cache:clear does that.
If you really want to clear the view cache, I think you have to write your own artisan command and call it as I said before, or entirely skip the artisan path and clear the view cache in some class that you call from a controller or a route.
But, my real question is do you really need to clear the view cache? In a project I’m working on now, I have almost 100 cached views and they weight less then 1 Mb, while my vendor directory is > 40 Mb. I don’t think view cache is a real bottleneck in disk usage and never had a real need to clear it.
Go to laravelFolder/bootstrap/cache then rename config.php to anything you want eg. config.php_old and reload your site. That should work like voodoo.
is it possible to use the code below with the new clear cache commands:
It’s not necessary to give the possibility to clear the caches to everyone, especially in a production enviroment, so I suggest to comment that routes and, when it’s needed, to de-comment the code and run the routes.
Config caching The laravel config spreads across dozens of files, and including every one of them for each request is a costly process. To combine all of your config files into one, use:
Keep in mind that any changes to the config will not have any effect once you cache it. To refresh the config cache, run the above command again. In case you want to completely get rid of the config cache, run
Routes caching Routing is also an expensive task in laravel. To cache the routes.php file run the below command:
Mind that it doesn’t work with closures. In case you’re using closures this is a great chance to move them into a controller, as the artisan command will throw an exception when trying to compile routes that are bound to closures instead of proper controller methods. In the same as the config cache, any changes to routes.php will not have any effect anymore. To refresh the cache, run the above command everytime you do a change to the routes file. To completely get rid of the route cache, run the below command:
Classmap optimization
It’s not uncommon for a medium-sized project to be spread across hundreds of PHP files. As good coding behaviours dictate us, everything has its own file. This, of course, does not come without drawbacks. Laravel has to include dozens of different files for each request, which is a costly thing to do.
Hence, a good optimization method is declaring which files are used for every request (this is, for example, all your service providers, middlewares and a few more) and combining them in only one file, which will be afterwards loaded for each request. This not different from combining all your javascript files into one, so the browser will have to make fewer requests to the server.
The additional compiles files (again: service providers, middlewares and so on) should be declared by you in config/compile.php, in the files key. Once you put there everything essential for every request made to your app, concatenate them in one file with:
Optimizing the composer autoload
This one is not only for laravel, but for any application that’s making use of composer.
I’ll explain first how the PSR-4 autoload works, and then I’ll show you what command you should run to optimize it. If you’re not interested in knowing how composer works, I recommend you jumping directly to the console command.
All this hard work only to get that the App\Controllers\AuthController class exists in the app/Controllers/AuthController.php file. In order to have composer scanning your entire application and create direct 1-to-1 associations of classes and files, run the following command:
Laravel clear file cache
I have changed file in Laravel public folder, but when I try to download using link, it downloads old file. I have tried:
php artisan route:cache
php artisan view:clear
php artisan config:cache
But without any success. Can someone help me?
3 Answers 3
It might be your browser that’s caching the file. Try download it again in a different browser or try in Incognito or Private Browsing mode to test it. I’ve had this same thing happen to me today actually and turns out the browser cached the file and kept reloading that file even after it was deleted from the server!
It’s because of your browser cache not blade cache.
Add a random number or better than that, the current time after the download links. like:
If you´re using artisan as server try to stop and restart it. Also you should try to reload the page by CTRL + F5 or CTRL + SHIFT + R which ignores the local browser cache.
Not the answer you’re looking for? Browse other questions tagged laravel or ask your own question.
Related
Hot Network Questions
Subscribe to RSS
To subscribe to this RSS feed, copy and paste this URL into your RSS reader.
site design / logo © 2021 Stack Exchange Inc; user contributions licensed under cc by-sa. rev 2021.9.16.40232
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.