mirror of
https://github.com/wintercms/winter.git
synced 2024-06-28 05:33:29 +02:00
c137760498
This will minimize changes when ConfigWriter is used to set config values through PHP.
35 lines
1.2 KiB
PHP
35 lines
1.2 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' => [
|
|
// Default Laravel Blade template location
|
|
// @see https://github.com/octobercms/october/issues/3473 & https://github.com/octobercms/october/issues/3459
|
|
// realpath(base_path('resources/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'))),
|
|
];
|