421fe33763
execute php artisan migrate to get theme_settings table
new commande available = create:theme-settings {theme_name?} Initialise les settings pour un nouveau theme
positionnement des blades dans un dossier défini par la nouvelle variable d'environnement APP_THEME (default : basic)
positionnement des ressources js et sass dans le dossier des blades du theme (pour mettre toute l'arboresence necessaire au thème sous une seule racine gitable)
37 lines
1.1 KiB
PHP
37 lines
1.1 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' => [
|
|
resource_path('views'),
|
|
resource_path('views/front/'.config('app.theme')),
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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'))
|
|
),
|
|
|
|
];
|