Compiled Blades on Heroku

Hey all, I'm trying to deploy a laravel application to heroku and I'm running into the issue of heroku's ephemeral filesystem (i.e. I can't write any file locally).

Is there an easy way I can configure compiled blades to write to a database or S3 storage instead?

I've changed all the filesystem configuration to use S3 for files and redis for cache and sessions - however blades STILL compile to the /storage/framework/views directory.

Thanks!

glockops

10 years ago

Level 1

I "fixed" the problem I was experiencing by adding a storage/framework/views/ folder to the application. Blade templates will not compile properly if that folder is missing. So while it "works" I'm not sure view cache is doing anything productive on the heroku ecosystem.

etherealite

9 years ago

Level 1

Were you able to find out if Laravel's view caching is screwy with the Heroku ephemeral filesystem?

Please or to participate in this conversation.