ce12d3cb89
upgraded laravel version from 5.0 to 5.2. Changed ORM from eloquent to Doctrine to support better inheritance handling basically eloquent does not suppor the inheritance model used by Silverstripe which makes dificult to implement write apis on model hierarchies defined with SS schema. Refactoring. Change-Id: I802e171c8b95e81dc21578543ddb6a02003985e5
34 lines
1020 B
PHP
34 lines
1020 B
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' => [
|
|
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' => realpath(storage_path('framework/views')),
|
|
|
|
];
|