Based on the code and documentation provided, I'll analyze whether the realtime compiler should save previewed pages by default.

Currently, the default behavior is to save preview pages (save_preview = true), as seen in:

    'server' => [
        // The default port the preview is served on
        'port' => env('SERVER_PORT', 8080),

        // The default host the preview is served on
        'host' => env('SERVER_HOST', 'localhost'),

        // Should preview pages be saved to the output directory?
        'save_preview' => true,

However, there are several factors to consider:

Purpose of Preview Server: The realtime compiler is meant for local development and previewing changes, as noted in:

The Hyde Realtime Compiler is included with Hyde installations and is what powers the `php hyde serve` command,
allowing you to preview your static site on a local development server without having to rebuild the site.

Development Focus: Hyde emphasizes developer experience and simplicity, as shown in:

- **Developer experience first:** Creating sites with Hyde and contributing to the framework should be a joy.
- **Zero config setup:** You should be able to just install Hyde and start building your project right away. Hyde should follow convention over configuration and come preconfigured with sensible defaults.
- **Customizable when you need it:** While configuration should not be a requirement, the option should always be there. As such, we should provide easy ways for customization to those who need it.

Storage Implications: Saving previews creates additional files that aren't necessarily needed for development purposes.
Change History: A change was made to add this configuration option, as noted in:

### Added
- Added a RealtimeCompiler config option to disable rendered pages being stored to disk in https://github.com/hydephp/develop/pull/1334

Recommendation:
The default should be changed to false because:

During development/preview, saving files is not typically expected or necessary
It creates unnecessary file operations and storage usage
The primary purpose of php hyde serve is for previewing changes, not generating files
If users need to save the files, they can explicitly enable this via configuration
This aligns better with the principle of least surprise - most developers would expect a preview server to just show changes without writing files

The current default of true seems to go against the expected behavior of a development preview server. The setting should remain configurable, but defaulting to false would be more intuitive and aligned with typical development workflows.

Uh oh!

Should the serve command save pages by default? #1994

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions