commit | author | age
|
9f6455
|
1 |
<?php |
DC |
2 |
|
|
3 |
return [ |
|
4 |
|
|
5 |
/* |
|
6 |
|-------------------------------------------------------------------------- |
|
7 |
| View Storage Paths |
|
8 |
|-------------------------------------------------------------------------- |
|
9 |
| |
|
10 |
| Most templating systems load templates from disk. Here you may specify |
|
11 |
| an array of paths that should be checked for your views. Of course |
|
12 |
| the usual Laravel view path has already been registered for you. |
|
13 |
| |
|
14 |
*/ |
|
15 |
|
|
16 |
'paths' => [ |
|
17 |
resource_path('views'), |
|
18 |
], |
|
19 |
|
|
20 |
/* |
|
21 |
|-------------------------------------------------------------------------- |
|
22 |
| Compiled View Path |
|
23 |
|-------------------------------------------------------------------------- |
|
24 |
| |
|
25 |
| This option determines where all the compiled Blade templates will be |
|
26 |
| stored for your application. Typically, this is within the storage |
|
27 |
| directory. However, as usual, you are free to change this value. |
|
28 |
| |
|
29 |
*/ |
|
30 |
|
|
31 |
'compiled' => env( |
|
32 |
'VIEW_COMPILED_PATH', |
|
33 |
realpath(storage_path('framework/views')) |
|
34 |
), |
|
35 |
|
|
36 |
]; |