53 lines
1.7 KiB
PHP
53 lines
1.7 KiB
PHP
<?php
|
|
|
|
return [
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| View Storage Paths
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Most templating systems load templates from disk. Here you may specify
|
|
| an array of paths that should be checked for your views. Of course
|
|
| the usual Laravel view path has already been registered for you.
|
|
|
|
|
*/
|
|
|
|
'paths' => [
|
|
resource_path('views'),
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Compiled View Path
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| This option determines where all the compiled Blade templates will be
|
|
| stored for your application. Typically, this is within the storage
|
|
| directory. However, as usual, you are free to change this value.
|
|
|
|
|
*/
|
|
|
|
'compiled' => env(
|
|
'VIEW_COMPILED_PATH',
|
|
realpath(storage_path('framework/views'))
|
|
),
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Compiled View Cache
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| Blade still needs a writable path to generate PHP for each request, but
|
|
| local development must not trust an existing compiled template. Setting
|
|
| the compiler cache flag to false makes Laravel recompile every view and
|
|
| leaves production's normal compiled-view behavior unchanged.
|
|
|--------------------------------------------------------------------------
|
|
*/
|
|
|
|
'cache' => env('APP_ENV', 'production') === 'local'
|
|
? false
|
|
: env('VIEW_CACHE', true),
|
|
|
|
];
|