Hey! Well noticed. We added that symlink so Rails app won't break, but as you can see it's not the ideal solution. I believe in Rails 3.1 the design behind asset caching will be reviewed and hopefully fixed, but in the meantime we recommend users to look for alternatives.
For instance, David (also from Heroku) wrote this one: http://github.com/ddollar/asset-resource I'm not familiar with all the options on this area, but I'm sure there are others. On Wed, Sep 29, 2010 at 9:29 AM, nevinera <[email protected]> wrote: > We are using 'javascript_include_tag :all, :cache => false' in our > application layout. The generated javascript includes are many, but > one of them is a link to 'javascript/all.js', which as I understand it > should not be listed. > > When I dug in, I found that there's an 'all.js' soft link in the app's > directory on heroku that points to /var/tmp/userapps/<id>/all.js - > that directory has some contents, but 'all.js' is not among them. > > Rails doesn't follow the soft link to see if there's actually a file > to serve; it just adds the include directive, causing every page to > receive a 404 for that javascript file. I expect this is part of > heroku's workaround for javascript caching on their read-only fs, but > why is there a soft link with no file? Is our app misbehaving in some > way? Has anybody run into this issue before, and did you find a > workaround/fix? > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
