- 基础环境:Docker 部署配置,源码挂载实时同步 - 修复:super_admin 权限补全、登录重定向循环 - 开发:店铺营销账户账单 - 抖音账户(15字段汇总账单) - 开发:店铺营销账户账单 - 淘系支付宝账户(8字段流水账单) - 开发:店铺营销账户账单 - 拼多多账户(7字段流水账单) - 业务页面导航集成:config/business_navigation.php + Business\Pages 控制器 - 各平台独立表结构和视图,互不影响
37 lines
1.0 KiB
PHP
37 lines
1.0 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'),
|
|
],
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| 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'))
|
|
),
|
|
|
|
];
|