Buckets:
| 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')) | |
| ), | |
| ]; | |
Xet Storage Details
- Size:
- 1.05 kB
- Xet hash:
- 13c196cf2df25de83f34caa434f2d06faf91a19940209b18cf72fd404b247b9b
·
Xet efficiently stores files, intelligently splitting them into unique chunks and accelerating uploads and downloads. More info.