3
Docs
runtime/ – Pretty much everything in here is there for caching and logging purposes. Nothing that Craft couldn’t live without, if the folder happened to get deleted.
It is safe to delete it
2
For anyone else trying this: the solution I eventually came up for was to follow these instructions for adding an argument to the Procfile to tell Heroku to tail Craft's log file into the "Logplex" stream.
There might well be situations where Brad's suggestion (using a plugin to write the logs to stderr) is preferable, but I wasn't sure what the ...
1
Imagick uses the /tmp folder by default, but you can change it: https://github.com/ImageMagick/ImageMagick/issues/399#issuecomment-285793433
1
You could try fronting Blob with s3proxy as a workaround.
1
Not super familiar with Heroku, but some Googling suggests and if you want to keep anything on a permanent (non-ephemeral) file system, most people use S3 for that.
There is the CRAFT_STORAGE_PATH PHP constant for both Craft 2 and 3, but it's currently assuming local file-system based paths and making it cloud based would cause a big performance hit anyway.
...
1
The easiest thing is to look it up. Craft CMS is usually really self-explaining So when you take a look at your folders in craft/storage/runtime/temp you'll see the following
/assets <- for example cached thumbnails/preview icons and all those things
/cache
/compiled_templates <- templates that have cache tags, that should only compiled once... for ...
Only top voted, non community-wiki answers of a minimum length are eligible