Reading this ( https://learn.getgrav.org/16/advanced/performance-and-caching#grav-core-caching ), I was under the impression that the hash method would actually hash the files (in a fast not-so-secure way as it is not the point.)

I guess that the idea is to not load the file from disk, making it faster. Here comes the issue: when deploying, you have to be careful or preserving file attributes

Describe the bug

The external documentation of this project is unavailable.
The site doesn't load.

To Reproduce...

Steps to reproduce the behavior (include code examples, if applicable):

• load https://uuid.ramsey.dev/en/latest/

Expected behavior

Documentation is displayed.

Is your feature request related to a problem? Please describe.
When using a proxy in front of the Daemon, the port defined in the Node setting for daemon has to be exposed on the Daemon´s server as the Panel will try to reach the Daemon on the defined port. When set to the proxied port (eg: 443) then the proxy will able to forward the frontend to the backend but as soon as you auto-deploy the