Ran into the same problem with a new Heroku app of ours. However, we've been running the file cache on an older app for over a year and never had problems. (Both are on the cedar stack.) Did you ever get to the bottom of this?
I assume it has something to do with Heroku's philosophy of read-only source code, but we should have the ephemeral file system so that shouldn't matter. On Wed, Jan 30, 2013 at 8:59 AM, Shahruk Khan <[email protected]>wrote: > Here's the thing - Heroku uses EC2, meaning that any files written are > deleted on Git push. But I think you're right, so I'm gonna contact Heroku > support the moment I get the chance. Thanks > > > On Wednesday, January 30, 2013 7:51:12 AM UTC-5, Luciano Bargmann wrote: >> >> First things first: I am almost sure you have a write permission problem. >> Have you tried to fix that? > > -- > Like Us on FaceBook https://www.facebook.com/CakePHP > Find us on Twitter http://twitter.com/CakePHP > > --- > You received this message because you are subscribed to the Google Groups > "CakePHP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/cake-php?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Brad Koch Email: [email protected] Phone: 989-372-1212 -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/cake-php?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
