diff options
| author | Max | 2019-05-13 15:50:36 +0200 |
|---|---|---|
| committer | Max | 2019-05-13 15:50:36 +0200 |
| commit | 7149647b729b2aa30d76346a7cc3da37c1c692ca (patch) | |
| tree | b773b7c02a3434ea46d12659302abc586b0fdb7b /config/view.php | |
| download | kategorischeraperitif-7149647b729b2aa30d76346a7cc3da37c1c692ca.tar.gz | |
Initial commit.
Diffstat (limited to 'config/view.php')
| -rw-r--r-- | config/view.php | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/config/view.php b/config/view.php new file mode 100644 index 0000000..2acfd9c --- /dev/null +++ b/config/view.php @@ -0,0 +1,33 @@ +<?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' => realpath(storage_path('framework/views')), + +]; |
