Help me understand the Blade compile process—how are hashed files served?

[jamesfacts]

Yikes… after a nice full day examining this issue I see Toby more or less laid out where I’ve run into a problem back in May.

@anon66789415

You need to have your compiled templates in the repo that have been compiled at the path for the specific site e.g. /nas/content/staging/${WPE_INSTALL}/wp-content/uploads/cache/xyz.php. You can’t even just take your local cache folder and upload it because Blade will look for files at a different HASH.php

WPEngine does not give you write permissions via PHP so the templates will never compile.

If you somehow managed to figure it out I’d love to know because I haven’t. I started working on a Docker container that would install wordpress in the directory, compile the templates. But I think I’d rather just drop Blade as a requirement.

That said… I am still a little stuck compiling at the correct path. For me, this command in the suggested deploy script:
git clone git@git.wpengine.com:${CI_ENVIRONMENT_NAME}/${WPE_INSTALL}.git $FOLDER

doesn’t yield a dir structure that matches the WPE /nas/content/staging/${WPE_INSTALL}/

…back to poking around.