Switch to zero-config setup, remove config and bootstrap dirs (#2839)
* Remove config directory * feat(zeroconfig): Add support for zero-config * test(php-lint): remove config directory * chore(readme): update dir structure * admin/customizer has been removed Co-authored-by: QWp6t <hi@qwp6t.me>
This commit is contained in:
@@ -1,41 +0,0 @@
|
||||
<?php
|
||||
|
||||
return [
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Default Assets Manifest
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Here you may specify the default asset manifest that should be used.
|
||||
| The "theme" manifest is recommended as the default as it cedes ultimate
|
||||
| authority of your application's assets to the theme.
|
||||
|
|
||||
*/
|
||||
|
||||
'default' => 'theme',
|
||||
|
||||
/*
|
||||
|--------------------------------------------------------------------------
|
||||
| Assets Manifests
|
||||
|--------------------------------------------------------------------------
|
||||
|
|
||||
| Manifests contain lists of assets that are referenced by static keys that
|
||||
| point to dynamic locations, such as a cache-busted location. We currently
|
||||
| support two types of manifest:
|
||||
|
|
||||
| assets: key-value pairs to match assets to their revved counterparts
|
||||
|
|
||||
| bundles: a series of entrypoints for loading bundles
|
||||
|
|
||||
*/
|
||||
|
||||
'manifests' => [
|
||||
'theme' => [
|
||||
'path' => get_theme_file_path('public'),
|
||||
'url' => get_theme_file_uri('public'),
|
||||
'assets' => public_path('manifest.json'),
|
||||
'bundles' => public_path('entrypoints.json'),
|
||||
]
|
||||
]
|
||||
];
|
||||
Reference in New Issue
Block a user