[9.x] Use Relative View Path Name When Hashing Compiled Views

[bogdankharchenko]

Issue

We are not able to "pre-compile" views on say a local machine/build box, and push it into prod "pre-compiled". This is because the filename of the cached view is a sha1 of the absolute path of the file. Meaning, if the directory is different on which the view was initially compiled, then the view is then recompiled.

This PR introduces a new basePath param into the the Compiler - which then allows us to take the absolute path of the view, and remove the base path from it - which is then used as the "name" before being hashed

Targeted into 9.x as this is a possible breaking change.

Driver behind this was during a vapor deploy, we can pre-compile the views (locally) into bootstrap/cache/views and serve them already compiled. Which is great for a read-only filesystem.

[dennisprudlo]

Why not simply call view:cache as part of the deployment process?

[bogdankharchenko]

@dennisprudlo yes I already do that. But this will allow for the ability to pre-compile views before packaging the app up in a container or deploying to read only file systems

[inxilpro]

I could definitely also see using this in a CI pipeline to pre-compile views before deploy.

[taylorotwell]

Please detail the breaking changes.

[bogdankharchenko]

@taylorotwell thinking more about this -- I actually do not see the breaking change anymore, as the basePath is now an optional param defaulting to an empty string.

Would you like me to retarget this into 8.x?

[taylorotwell]

I placed this behind a new view.relative_hash configuration option to minimize risk of breakage. Defaults to false.