edenspiekermann / craft3-heroku-starterkit Goto Github PK

First of all, thank you for creating this repository. It has been a headstart and I've been very happy to use it. There's one issue I can't wrap our heads around; which is the filesystem of Heroku. I've been outsourcing image/asset storage to Amazon S3 which works quite well with the tools provided for Craft. However, caching and specifically anything happening in the /storage directory is quite a pain.

I experience loading times from 5 seconds and up on a 1x Dyno from Heroku, whereas in our local setup, this isn't happening (it's around 300ms). I've been trying to use /tmp path and even file_put_contents() without craft is not working there (no error, it just gets ignored). I am quite curious how you cope with this challenge.

Thanks in advance. Cheers!

There are a few options for logging Craft logs and errors with Heroku. Can you recommend one?

We have tried piping our logs to stdout using the Procfile, but we are still missing some important output.

web: vendor/bin/heroku-php-nginx -C docker/nginx/heroku.conf -l storage/logs/craft.log -l storage/logs/web.log -l storage/runtime/logs/app.log -l storage/logs/phperrors.log -l storage/logs/console.log -l storage/logs/feedme.log -l storage/logs/queue.log web/