5清除缓存laravel共享托管服务器 Laravel 5 - Clear cache in shared hosting server

我可以看到：http://itsolutionstuff.com/post/laravel-5-clear-cache-from-route-view-config-and-all-cache-data-from-applicationexample.html

可以使用下面的代码与新的清除缓存的命令：

//Clear Cache facade value:
Route::get('/clear-cache', function() {
    $exitCode = Artisan::call('cache:clear');
    return '<h1>Cache facade value cleared</h1>';
});

//Reoptimized class loader:
Route::get('/optimize', function() {
    $exitCode = Artisan::call('optimize');
    return '<h1>Reoptimized class loader</h1>';
});

//Route cache:
Route::get('/route-cache', function() {
    $exitCode = Artisan::call('route:cache');
    return '<h1>Routes cached</h1>';
});

//Clear Route cache:
Route::get('/route-clear', function() {
    $exitCode = Artisan::call('route:clear');
    return '<h1>Route cache cleared</h1>';
});

//Clear View cache:
Route::get('/view-clear', function() {
    $exitCode = Artisan::call('view:clear');
    return '<h1>View cache cleared</h1>';
});

//Clear Config cache:
Route::get('/config-cache', function() {
    $exitCode = Artisan::call('config:cache');
    return '<h1>Clear Config cleared</h1>';
});

给清除缓存每个人都可能是不必要的，尤其是在生产环境中，所以我建议评论路线，当需要的时候，去评论的代码和运行路线。

基本上我想清除视图缓存。

现在有5.1个命令，laravel

php artisan view:clear

我希望这有助于人

去laravelFolder/bootstrap/cache然后重命名config.php要你想要的任何东西，如config.php_old并重新加载你的网站。那应该像巫术。

快乐编码…

配置缓存配置的laravel遍布几十个文件，和including他们每个人的每个请求是一个昂贵的过程。把你所有的配置文件为一体，使用：1

php artisan config:cache

记住配置的任何更改将不会有任何影响你一旦缓存它。刷新配置缓存，再次运行上面的命令。如果你想彻底摆脱配置缓存，润1

php artisan config:clear

路由缓存路由也是一个昂贵的任务在laravel。缓存routes.php文件运行以下命令：1

php artisan route:cache

记住，它不工作与关闭。如果你使用闭包这是移动到控制器的好机会，为工匠命令将抛出一个异常，当试图编译的路线，必然会倒闭而不是一个适当的控制器的方法。在同等配置的缓存，以routes.php任何变化将不会有任何影响。刷新缓存，运行上面的命令，每次你改变路线文件。完全摆脱了路由缓存，运行下面的命令：1

php artisan route:clear

ClassMap优化

它是分布在数百个大中型项目的PHP文件并不罕见。良好的编码行为支配我们，凡事都有它自己的文件。这，当然，并不是没有缺点。Laravel：对于每个请求不同的数十个文件，这是要做一个昂贵的事。

因此，一个好的优化方法是声明这些文件用于为每个请求（这是，例如，你所有的服务提供商、中间件和一些），只有一个文件结合起来，将每个请求之后加载。这不同于将所有JavaScript文件合并成一个，所以浏览器会减少对服务器的请求。

额外的编译文件（一次：服务提供商、中间件等）应宣布你在配置文件中的关键compile.php。一旦你把这一切必不可少的了你的应用程序的每个请求，将它们串联在一个文件中：1

php artisan optimize --force

作曲家自动优化

这是一个不仅用于laravel，但任何应用程序，利用作曲家。

我会先解释如何psr-4加载工作，然后我会告诉你什么是命令你应该运行优化。如果你不知道作曲家的作品感兴趣，我建议你直接跳到控制台命令。

当你问compsoser为应用程序\控制器\ authcontroller类，它首先搜索在ClassMap直接关联。这是一个与ClassMap类和文件的1对1的关联数组。因为，当然，你没有手动添加登录类及其相关的文件到ClassMap，作曲家将搜索命名空间中，因为应用程序是一个psr-4命名空间，这是默认情况下，Laravel和它的应用程序/文件夹关联，作曲家将尝试转换psr-4类名称基本的字符串操作程序文件名。最后，它猜测程序\控制器\ authcontroller必须位于一个authcontroller.php文件，这是一个控制器/文件夹应该幸运的是命名空间中的文件夹，这是应用程序/。

这一切的努力只获得应用程序\控制器\ authcontroller类存在于应用程序/控制器/ authcontroller.php文件。为了扫描您的整个应用程序和作曲家创造的类和文件的直接一对一关联，运行以下命令：1

composer dumpautoload -o

记住，如果你已经跑php工匠优化力，你不用跑这一个了。由于优化命令已经告诉作曲家创造一个优化的加载。

你可以通过FTP和清除存储\框架视图用于laravel 5存储\意见laravel 4或应用程序文件夹连接。

As I can see:http://itsolutionstuff.com/post/laravel-5-clear-cache-from-route-view-config-and-all-cache-data-from-applicationexample.html

is it possible to use the code below with the new clear cache commands:

//Clear Cache facade value:
Route::get('/clear-cache', function() {
    $exitCode = Artisan::call('cache:clear');
    return '<h1>Cache facade value cleared</h1>';
});

//Reoptimized class loader:
Route::get('/optimize', function() {
    $exitCode = Artisan::call('optimize');
    return '<h1>Reoptimized class loader</h1>';
});

//Route cache:
Route::get('/route-cache', function() {
    $exitCode = Artisan::call('route:cache');
    return '<h1>Routes cached</h1>';
});

//Clear Route cache:
Route::get('/route-clear', function() {
    $exitCode = Artisan::call('route:clear');
    return '<h1>Route cache cleared</h1>';
});

//Clear View cache:
Route::get('/view-clear', function() {
    $exitCode = Artisan::call('view:clear');
    return '<h1>View cache cleared</h1>';
});

//Clear Config cache:
Route::get('/config-cache', function() {
    $exitCode = Artisan::call('config:cache');
    return '<h1>Clear Config cleared</h1>';
});

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.

Basically I want to clear the views cache.

There is now a command in Laravel 5.1 for that

php artisan view:clear

I hope this helps someone

Go tolaravelFolder/bootstrap/cachethen renameconfig.phpto anything you want eg.config.php_oldand reload your site. That should work like voodoo.

Happy Coding...

Config cachingThe laravel config spreads across dozens of files, andincludingevery one of them for each request is a costly process. To combine all of your config files into one, use:1

php artisan config:cache

Keep in mind that any changes to the config will not have any effect once you cache it it. To refresh the config cache, run the above command again. In case you want to completely get rid of the config cache, run1

php artisan config:clear

Routes cachingRouting is also an expensive task in laravel. To cache the routes.php file run the below command:1

php artisan route:cache

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 a 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:1

php artisan route:clear

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:1

php artisan optimize --force

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.

When you ask compsoser for the App\Controllers\AuthController class, it first searches for a direct association in the classmap. The classmap is an array with 1-to-1 associations of classes and files. Since, of course, you did not manually add the Login class and its associated file to the classmap, composer will move on and search in the namespaces.Because App is a PSR-4 namespace, which comes by default with Laravel and it's associated to the app/ folder, composer will try converting the PSR-4 class name to a filename with basic string manipulation procedures. In the end, it guesses that App\Controllers\AuthController must be located in a AuthController.php file, which is in a Controllers/ folder that should luckily be in the namespace folder, which is app/.

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:1

composer dumpautoload -o

Keep in mind that if you already ran php artisan optimize --force, you don't have to run this one anymore. Since the optimize command already tells composer to create an optimized autoload.

You can connect via FTP and clear storage\framework\views folder for laravel 5 or app\storage\views for laravel 4.