Run php artisan cache:clear to clear the application cache; 2. Run php artisan route:clear to clear the route cache; 3. Run php artisan config:clear to clear the configuration cache; 4. Run php artisan view:clear to clear the view cache; 5. Optionally execute composer dump-autoload to regenerate the class map; in development, these commands can be executed in turn to completely clear the cache. After the production environment is cleared, config:cache and route:cache should be re-executed to improve performance. The problem is usually solved by cache:clear and view:clear.
Clearing cache in Laravel is a common task during development, especially after making changes to routes, configuration files, or views. Laravel provides several Artisan commands to clear different types of cache. Here's how to do it properly.

1. Clear Application Cache
Laravel stores cached data like configuration, routes, and compiled views. To clear the main application cache, run:
php artisan cache:clear
This command removes cached data stored via the Cache
facade (eg, data cached with Cache::put()
or similar methods), usually located in storage/framework/cache/data
.

? This is safe to run in production and won't affect your views or configuration once they're reloaded.
2. Clear Route Cache
If you've cached your routes using route:cache
, you need to clear the route cache separately:

php artisan route:clear
This deletes the cached bootstrap/cache/routes-v7.php
file (or similar versioned file). After running this, Laravel will use your live route files again.
?? Always run
route:clear
if you get route-related issues after deployment or if you're unable to see new routes.
3. Clear Configuration Cache
If you used config:cache
(common in production), Laravel caches your config files into a single file. To clear it:
php artisan config:clear
This removes bootstrap/cache/config.php
. After clearing, Laravel will load config files individually again.
? Useful when you update
.env
values or config files and they aren't taking effect.
4. Clear Compiled Views
Blade views are compiled into PHP code and cached for performance. To clear them:
php artisan view:clear
This deletes files in storage/framework/views/
. Use this if your Blade template changes aren't showing up.
You can also clear specific types:
- Clear all views:
php artisan view:clear
- Clear cached views for a specific environment: not directly supported, but the above command works universally.
5. Optional: Clear Compiled Classes (Optimize Cache)
If you've run php artisan optimize
(deprecated in newer Laravel versions), or used composer dump-autoload
, you might want to regenerate the class map:
composer dump-autoload
In Laravel 5.6 , this isn't needed often, but it helps if you're adding custom classes not in PSR-4.
Common Full Cache Reset (During Development)
If you're troubleshooting and want to clear everything , run these commands in order:
php artisan cache:clear php artisan route:clear php artisan config:clear php artisan view:clear
Or create a script or alias for faster execution.
? Pro tip: You can combine them in one line (on Unix-like systems):
php artisan cache:clear && php artisan route:clear && php artisan config:clear && php artisan view:clear
Bonus: Re-cache Everything (For Production)
After clearing, in production, you may want to re-cache for performance:
php artisan config:cache php artisan route:cache
?? Don't cache config/routes in local development — it makes debugging harder.
Basically, just use the right php artisan
command depending on what's cached. Most issues are solved with cache:clear
and view:clear
.
The above is the detailed content of How to clear cache in Laravel?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

There are three main ways to set environment variables in PHP: 1. Global configuration through php.ini; 2. Passed through a web server (such as SetEnv of Apache or fastcgi_param of Nginx); 3. Use putenv() function in PHP scripts. Among them, php.ini is suitable for global and infrequently changing configurations, web server configuration is suitable for scenarios that need to be isolated, and putenv() is suitable for temporary variables. Persistence policies include configuration files (such as php.ini or web server configuration), .env files are loaded with dotenv library, and dynamic injection of variables in CI/CD processes. Security management sensitive information should be avoided hard-coded, and it is recommended to use.en

To enable PHP containers to support automatic construction, the core lies in configuring the continuous integration (CI) process. 1. Use Dockerfile to define the PHP environment, including basic image, extension installation, dependency management and permission settings; 2. Configure CI/CD tools such as GitLabCI, and define the build, test and deployment stages through the .gitlab-ci.yml file to achieve automatic construction, testing and deployment; 3. Integrate test frameworks such as PHPUnit to ensure that tests are automatically run after code changes; 4. Use automated deployment strategies such as Kubernetes to define deployment configuration through the deployment.yaml file; 5. Optimize Dockerfile and adopt multi-stage construction

When choosing a suitable PHP framework, you need to consider comprehensively according to project needs: Laravel is suitable for rapid development and provides EloquentORM and Blade template engines, which are convenient for database operation and dynamic form rendering; Symfony is more flexible and suitable for complex systems; CodeIgniter is lightweight and suitable for simple applications with high performance requirements. 2. To ensure the accuracy of AI models, we need to start with high-quality data training, reasonable selection of evaluation indicators (such as accuracy, recall, F1 value), regular performance evaluation and model tuning, and ensure code quality through unit testing and integration testing, while continuously monitoring the input data to prevent data drift. 3. Many measures are required to protect user privacy: encrypt and store sensitive data (such as AES

Laravel's configuration cache improves performance by merging all configuration files into a single cache file. Enabling configuration cache in a production environment can reduce I/O operations and file parsing on each request, thereby speeding up configuration loading; 1. It should be enabled when the application is deployed, the configuration is stable and no frequent changes are required; 2. After enabling, modify the configuration, you need to re-run phpartisanconfig:cache to take effect; 3. Avoid using dynamic logic or closures that depend on runtime conditions in the configuration file; 4. When troubleshooting problems, you should first clear the cache, check the .env variables and re-cache.

To build a PHP content payment platform, it is necessary to build a user management, content management, payment and permission control system. First, establish a user authentication system and use JWT to achieve lightweight authentication; second, design the backend management interface and database fields to manage paid content; third, integrate Alipay or WeChat payment and ensure process security; fourth, control user access rights through session or cookies. Choosing the Laravel framework can improve development efficiency, use watermarks and user management to prevent content theft, optimize performance requires coordinated improvement of code, database, cache and server configuration, and clear policies must be formulated and malicious behaviors must be prevented.

User permission management is the core mechanism for realizing product monetization in PHP development. It separates users, roles and permissions through a role-based access control (RBAC) model to achieve flexible permission allocation and management. The specific steps include: 1. Design three tables of users, roles, and permissions and two intermediate tables of user_roles and role_permissions; 2. Implement permission checking methods in the code such as $user->can('edit_post'); 3. Use cache to improve performance; 4. Use permission control to realize product function layering and differentiated services, thereby supporting membership system and pricing strategies; 5. Avoid the permission granularity is too coarse or too fine, and use "investment"

The core idea of PHP combining AI for video content analysis is to let PHP serve as the backend "glue", first upload video to cloud storage, and then call AI services (such as Google CloudVideoAI, etc.) for asynchronous analysis; 2. PHP parses the JSON results, extract people, objects, scenes, voice and other information to generate intelligent tags and store them in the database; 3. The advantage is to use PHP's mature web ecosystem to quickly integrate AI capabilities, which is suitable for projects with existing PHP systems to efficiently implement; 4. Common challenges include large file processing (directly transmitted to cloud storage with pre-signed URLs), asynchronous tasks (introducing message queues), cost control (on-demand analysis, budget monitoring) and result optimization (label standardization); 5. Smart tags significantly improve visual

Laravel's EloquentScopes is a tool that encapsulates common query logic, divided into local scope and global scope. 1. The local scope is defined with a method starting with scope and needs to be called explicitly, such as Post::published(); 2. The global scope is automatically applied to all queries, often used for soft deletion or multi-tenant systems, and the Scope interface needs to be implemented and registered in the model; 3. The scope can be equipped with parameters, such as filtering articles by year or month, and corresponding parameters are passed in when calling; 4. Pay attention to naming specifications, chain calls, temporary disabling and combination expansion when using to improve code clarity and reusability.
