Skip to content

Commit d03e7b7

Browse files
authored
Merge pull request #1532 from hydephp/document-advanced-configuration-options
Document advanced configuration options
2 parents 56f18dc + e24815a commit d03e7b7

File tree

1 file changed

+59
-0
lines changed

1 file changed

+59
-0
lines changed

docs/digging-deeper/customization.md

Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -363,6 +363,65 @@ This feature is enabled by default, so you only need to place your pages in subd
363363

364364
For example: `_docs/getting-started/installation.md` will be placed in a group called "Getting Started".
365365

366+
## Additional Advanced Options
367+
368+
The following configuration options in the `confg/hyde.php` file are intended for advanced users and
369+
should only be modified if you fully understand their impact. The code examples show the default values.
370+
371+
### `media_extensions`
372+
373+
This option allows you to specify file extensions considered as media files, which will be copied to the output directory.
374+
To add more extensions, either append them to the existing array or override the entire array.
375+
376+
```php
377+
// filepath config/hyde.php
378+
use \Hyde\Support\Filesystem\MediaFile;
379+
380+
'media_extensions' => array_merge([], MediaFile::EXTENSIONS),
381+
```
382+
383+
### `safe_output_directories`
384+
385+
This setting defines a list of directories deemed safe to empty during the site build process as a safeguard to prevent accidental data loss.
386+
If the site output directory is not in this list, the build command will prompt for confirmation before emptying it. It is preconfigured
387+
with common directories including the default one, but you are free to change this to include any custom directories you may need.
388+
389+
```php
390+
// filepath config/hyde.php
391+
'safe_output_directories' => ['_site', 'docs', 'build'],
392+
```
393+
394+
### `generate_build_manifest`
395+
396+
Determines whether a JSON build manifest with metadata about the build should be generated. Set to `true` to enable.
397+
398+
```php
399+
// filepath config/hyde.php
400+
'generate_build_manifest' => true,
401+
```
402+
403+
### `build_manifest_path`
404+
405+
Specifies the path where the build manifest should be saved, relative to the project root.
406+
407+
```php
408+
// filepath config/hyde.php
409+
'build_manifest_path' => 'app/storage/framework/cache/build-manifest.json',
410+
```
411+
412+
### `hydefront_version` and `hydefront_cdn_url`
413+
414+
These options allow you to specify the HydeFront version and CDN URL when loading `app.css` from the CDN.
415+
416+
Only change these if you know what you're doing as some versions may incompatible with your Hyde version.
417+
418+
```php
419+
// filepath config/hyde.php
420+
use \Hyde\Framework\Services\AssetService;
421+
422+
'hydefront_version' => AssetService::HYDEFRONT_VERSION,
423+
'hydefront_cdn_url' => AssetService::HYDEFRONT_CDN_URL,
424+
```
366425

367426
## Blade Views
368427

0 commit comments

Comments
 (0)