| 1 | 1 |
new file mode 100644 |
| ... | ... |
@@ -0,0 +1,33 @@ |
| 1 |
+<?php |
|
| 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' => realpath(storage_path('framework/views')),
|
|
| 32 |
+ |
|
| 33 |
+]; |