Add a safer output directory config option to replace deprecated setting #106
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About
The
hyde.site_output_path
option was recently deprecated. This update adds an alternative which resolves the relative path within the service provider. This makes it safer to set the output directory to something within the project. If one wants to use an absolute path outside the project that must be done in a service provider, which has now been documented.If you want to store your compiled website in a different directory than the default
_pages
, you can change the path using the following configuration option in config/hyde.php. The path is expected to be relative to your project root.Setting an absolute path
If you want to store the output website outside your project with an absolute path you may do so at your own risk using a service provider. This is not supported or recommended as it may cause unintentional file deletions.